How ACP Works
- Agent collects intent — The AI agent gathers order details and payment authorization through natural conversation.
- ACP handler validates — The handler validates the order against your catalog, pricing rules, and inventory.
- Payment authorized — Scoped payment authorization ensures the agent can only charge approved amounts.
- Order created — The order is created in your commerce platform via the Sync Server.
Key Concepts
Why This Design
- Deterministic checkout — Orders are validated server-side, never by the LLM.
- Scoped payments — Agents can only charge amounts the customer explicitly authorizes.
- Auditable — Every step is logged with full traceability.
- Platform-agnostic — Works with any commerce backend through bindings.
When to Use ACP
- Conversational checkout — Let customers buy through chat or voice interfaces.
- Delegated payments — Authorize agents to make purchases on behalf of users with spending limits.
- Unified agent workflows — Single protocol for multiple AI assistants (ChatGPT, custom agents, voice bots).
- B2B ordering — Streamline wholesale and recurring orders through conversational interfaces.
Quickstart
Use the Sync ACP reference and your tenant’s provisioned connection. The earlier wrapper example used an unpublished SDK and has been removed. Start with the ACP quickstart, then verify each downstream result independently. Order submission and payment settlement are separate outcomes.Further reading
- ACP async processing — long-running checkouts
- ACP routing — directing a request to the right merchant
- ACP schemas — the message shapes on the wire
Next steps
ACP overview
The protocol in full, and where it came from.
ACP quickstart
A working checkout, end to end.
ACP endpoints
The HTTP surface to call until the SDK ships.
Agentic commerce checkout
The buyer-facing flow this enables.