insimbi

Docs · Agent protocols

x402

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

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.
x402 with insimbi in the pathSequence diagram with 4 lanes (Client (agent), Merchant API, insimbi, Facilitator (regulated partner)) and 14 numbered steps. The same steps are listed in text below the diagram.Client(agent)Merchant APIinsimbiFacilitator(regulated partner)1Request a resource2Price it and checkyour rules for whichassets and networksto accept3402 Payment Requiredwith aPAYMENT-REQUIREDheader4Retry with a signedpayment in thePAYMENT-SIGNATUREheader5Check the paymentagainst your rulesand the agent'smandate6POST /verify7Verification result(isValid, payer)8Allowed9Perform the work10Settle11POST /settle12Settlement result(success,transaction, network)13Write the ledger entry and fee lines tothe record14Return the resourcewith aPAYMENT-RESPONSEheader

Steps in text

  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

Request access

insimbi is in early access with design partners.