# x402

HTTP 402 payments from agents, verified and settled through a regulated partner.

Cohorts: Mm + Sc

**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.

**x402 with insimbi in the path.** Designed. Follows the x402 HTTP flow: 402, signed retry, verify, work, settle.

Lanes: Client (agent), Merchant API, insimbi, Facilitator (regulated partner)

1. Client (agent) to Merchant API: Request a resource
2. Merchant API to insimbi: Price it and check your rules for which assets and networks to accept
3. Merchant API to Client (agent): 402 Payment Required with a PAYMENT-REQUIRED header
4. Client (agent) to Merchant API: Retry with a signed payment in the PAYMENT-SIGNATURE header
5. Merchant API to insimbi: Check the payment against your rules and the agent's mandate
6. insimbi to Facilitator (regulated partner): POST /verify
7. Facilitator (regulated partner) to insimbi: Verification result (isValid, payer)
8. insimbi to Merchant API: Allowed
9. Merchant API: Perform the work
10. Merchant API to insimbi: Settle
11. insimbi to Facilitator (regulated partner): POST /settle
12. Facilitator (regulated partner) to insimbi: Settlement result (success, transaction, network)
13. insimbi: Write the ledger entry and fee lines to the record
14. Merchant API to Client (agent): Return the resource with a PAYMENT-RESPONSE header

- [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._