# Agentic Commerce Protocol (ACP)

Checkout sessions and a delegated payment token, charged by insimbi for the merchant.

Cohorts: Mm + Fi

**Designed.** Protocol support is designed. The flow follows the protocol's published specification, with insimbi on the merchant side. Every check and every settlement is written to the record.

**Agentic Commerce Protocol (ACP).** Designed. ACP checkout sessions and a delegated payment token, with insimbi charging for the merchant.

Lanes: Agent, Merchant, insimbi, Delegated payment provider

1. Agent to Merchant: POST /checkout_sessions (line items, currency)
2. Merchant to Agent: 201 with the authoritative cart, totals and fulfilment options
3. Agent to Merchant: POST /checkout_sessions/{id} to update choices
4. Agent to Delegated payment provider: POST /agentic_commerce/delegate_payment with an allowance
5. Delegated payment provider to Agent: Delegated token id
6. Agent to Merchant: POST /checkout_sessions/{id}/complete with payment_data
7. Merchant to insimbi: Charge the delegated token
8. insimbi: Check your rules and the allowance, choose the rail
9. insimbi to Delegated payment provider: Redeem the token within its allowance
10. Delegated payment provider to insimbi: Result
11. insimbi to Merchant: Result, written to the record
12. Merchant to Agent: Completed checkout and order

- [All flows](/docs/flows/): Every sequence diagram, linked to its section.
- [Integrations](/integrations/#protocols): Every agent protocol and rail we connect.
- [MCP tools](/docs/mcp/): insimbi as tools for any MCP client.

Request access: sales@insimbi.net

_insimbi is in early access with design partners._