facilitator
A trusted intermediary role in the x402 protocol architecture, responsible for verifying payment signatures, broadcasting transactions and bearing gas fees, so that a server can trust that payment has occurred before block confirmation.
Timeline (last 90 days)
In the x402 flow, the Worker POSTs the signed payload to the facilitator's /verify endpoint for validation, executes the business logic after validation passes, and finally calls /settle to settle; the Worker itself does not touch private keys, manage funds, or run blockchain nodes.
In the x402 protocol, the facilitator is a separate intermediary service responsible for /verify, which checks the validity of the payment signature (amount, payee, validity period, nonce, etc.), and /settle, which broadcasts the transaction and pays gas to complete the USDC transfer.
In one real run, three payment attempts triggered a server 500 after the payment-signature was accepted, the facilitator never broadcast, and the payer's balance changed only on another successful settlement—three signatures, zero on-chain settlement on the failed attempts.
Sampling 20,462 active x402 resources in the discovery index of a certain facilitator (one hundred at each of six scattered offset points), not a single one declared an extension that would issue counterparty receipts.
Seven of the eight facilitator endpoints returned no usable JSON on that path, so these count as "not measured" rather than "zero," including the largest index among them.
In the x402 ecosystem, it is often the facilitator, rather than the client itself, that actually broadcasts the payment on-chain, confirms the result and returns the credential to the seller.
Batch settlement is a layer used by the client and the facilitator it routes through to decide when to actually put these authorizations on-chain, and in theory does not require the endpoint to modify pricing or the challenge structure.
The marginal cost of blockchain settlement is mainly reflected in Gas fees rather than proportional commissions, and x402's facilitator model can further externalize this portion of the cost.
In the x402 response, the feePayer field indicates that the facilitator will bear the Gas fees, so the Agent only needs to hold USDC to complete payment and does not need to maintain a SOL balance.
All Facts (9)
In the x402 protocol, the facilitator is a separate intermediary service responsible for /verify, which checks the validity of the payment signature (amount, payee, validity period, nonce, etc.), and /settle, which broadcasts the transaction and pays gas to complete the USDC transfer.
50%UnverifiedIn the x402 flow, the Worker POSTs the signed payload to the facilitator's /verify endpoint for validation, executes the business logic after validation passes, and finally calls /settle to settle; the Worker itself does not touch private keys, manage funds, or run blockchain nodes.
50%UnverifiedSampling 20,462 active x402 resources in the discovery index of a certain facilitator (one hundred at each of six scattered offset points), not a single one declared an extension that would issue counterparty receipts.
50%UnverifiedSeven of the eight facilitator endpoints returned no usable JSON on that path, so these count as "not measured" rather than "zero," including the largest index among them.
50%UnverifiedBatch settlement is a layer used by the client and the facilitator it routes through to decide when to actually put these authorizations on-chain, and in theory does not require the endpoint to modify pricing or the challenge structure.
50%UnverifiedIn the x402 ecosystem, it is often the facilitator, rather than the client itself, that actually broadcasts the payment on-chain, confirms the result and returns the credential to the seller.
50%UnverifiedIn the x402 response, the feePayer field indicates that the facilitator will bear the Gas fees, so the Agent only needs to hold USDC to complete payment and does not need to maintain a SOL balance.
50%UnverifiedThe marginal cost of blockchain settlement is mainly reflected in Gas fees rather than proportional commissions, and x402's facilitator model can further externalize this portion of the cost.
50%UnverifiedIn one real run, three payment attempts triggered a server 500 after the payment-signature was accepted, the facilitator never broadcast, and the payer's balance changed only on another successful settlement—three signatures, zero on-chain settlement on the failed attempts.
50%