Integrated merchants
Merchants connected to the Agnic network — a structured catalogue and a server-to-server checkout.
Integrated merchants
When a merchant connects to Agnic, ordering no longer drives a browser. The merchant publishes a catalogue and exposes a checkout endpoint, and Agnic orders server to server — structured, authoritative, and fully deterministic. There is nothing to Explore: the merchant hands the engine its catalogue and a checkout endpoint up front, so an order is just Pay, server to server.
This is the richer, faster rail. It is also the smaller one: it covers the merchants you have a relationship with and can ask to connect. For everyone else — most of the internet — see Un-integrated merchants.
What "integrated" means
- A canonical catalogue. The merchant publishes its products to Agnic — a feed (CSV or JSONL) or the discover service. Prices, currency, and tax are authoritative; the agent never guesses a total.
- A server-to-server checkout. Agnic creates and completes a checkout session against the merchant's endpoint over a signed, server-to-server protocol (the Agentic Commerce Protocol). There is no page to read and no form to fill.
- Structured fulfilment. The merchant returns real fulfilment options — pickup, delivery zones, fees, ETAs — and the order is bound to the option the user chose during Explore.
How it differs at order time
| Integrated | Un-integrated | |
|---|---|---|
| Catalogue | Authoritative feed | Read from the live site |
| Total | Merchant-computed, exact | Recomputed and confirmed |
| Checkout | Server-to-server session | The merchant's web checkout |
| Fulfilment | Structured options | As the page offers |
| Determinism | Full | Self-healing replay |
The order surface for your agent is identical on both rails — the same Explore then Pay, the same mandate, the same confirmation, the same audit trail. Integration changes how Agnic talks to the merchant, not how the agent talks to Agnic. An agent built against one rail works against the other unchanged.
Onboarding a merchant
Two paths, depending on how the merchant wants to connect:
- Catalogue + checkout endpoint. The merchant publishes a product feed and implements the Agentic Commerce Protocol checkout endpoint. Agnic then orders server to server, with the merchant authoritative for price and fulfilment.
- Hosted onboarding. For merchants on a supported processor, Agnic offers one-click hosted onboarding (for example, Stripe Connect Standard) — the merchant connects its existing account, with no merchant code changes, and orders dispatch server to server against it.
Either way, the merchant remains the seller of record and charges through its own processor.
When to prefer it
- You need authoritative pricing and structured fulfilment — delivery fees, zones, ETAs.
- You want the highest determinism and the lowest latency.
- The merchant is one you can ask to connect.
For the long tail you cannot ask to integrate, the un-integrated rail completes the same order on the merchant's existing checkout.