Standards
we build on

The payment protocol Tollex speaks: 402 terms, payment payloads, settlement responses, version 2.

The normative protocol: the PaymentRequired object, payment payloads, the facilitator /verify and /settle interface, and payment flows per scheme.

Exact, upto and batch settlement, including how each binds a payment to a recipient, spender or channel. Tollex executes external routes only where that binding allows it.

Resource servers choose the facilitator that verifies and settles their payments. On an external route the merchant's facilitator settles; Tollex reads the outcome from the chain.

Tollex pins its client and server libraries and verifies the deployed x402 contracts against their published builds.

The metadata Tollex attaches to every payment challenge so catalogues can list its resources, and the catalogues it reads to find external merchants.

How payment rides on A2A messages; Tollex's A2A endpoint follows it.

The network Tollex settles on: chain ids, RPC endpoints and network behaviour.

Robinhood Chain is built on Arbitrum Nitro; Tollex's settlement assurance levels follow its finality model.

The stablecoin every Tollex payment is denominated in.

The issuer's technical documentation for USDG.

The signed transfer behind exact payments; the payer signs, a facilitator submits.

The signing format for payment authorizations and Tollex receipts.

Gas-sponsored approvals to Permit2 where a facilitator offers them.

Balances, allowances and transfer events that Tollex reads to reconcile payments.

How networks are named in payment terms and constraints, such as eip155:46630.

The approval and transfer contract behind upto payments and exact payments without EIP-3009.

The deployed bytecode Tollex compares against before trusting a chain.

The tool protocol of the Tollex MCP server, over stdio and Streamable HTTP.

The agent card and JSON-RPC interface Tollex publishes, versions 1.0 and 0.3.

The plain-text orientation file each Tollex service serves for model-driven agents.

Tollex imports provider APIs from OpenAPI and describes its own routes in it.

Every capability's input and output contract.

Canonical bytes for hashing quotes and receipts.

The client-credentials flow for providers that use OAuth.

The threat model behind Tollex's guarded outbound fetch for providers and discovery.