The x402 facilitator page explains how wallet-mediated payment flows relate to market-data access without turning billing mechanics into a REST market-data route. The facilitator is a public payment-infrastructure surface. It is not a market-data endpoint, not the REST API, and not a replacement for API-key authentication. It helps x402 resource servers verify and settle exact EVM payments on supported networks.Documentation Index
Fetch the complete documentation index at: https://docs.0xarchive.io/llms.txt
Use this file to discover all available pages before exploring further.
Facilitator Model
| Layer | Role |
|---|---|
| Public facilitator | Verifies and settles exact EVM payment data |
| Resource server | Defines paid routes, accepted networks, price, and recipient |
| Client signer | Signs exact payment authorization |
| 0xArchive market-data API | Optional resource protected by a server; still has its own route and response contract |
Public Endpoint Roles
| Endpoint role | Use |
|---|---|
| Supported networks | Check live network, scheme, and signer support |
| Verify | Check payment data before settlement |
| Settle | Submit an authorized payment for settlement |
| Health | Inspect facilitator liveness |
Payment Boundary Packet
Use this page when the job is x402 payment infrastructure, paid-resource settlement, or wallet-mediated access design. Keep the payment decision separate from the market-data decision.| Question | Route the work here |
|---|---|
| Which networks and schemes are supported? | Check the facilitator-supported-networks endpoint before configuring a paid resource. |
| Did the client sign an exact payment authorization? | Use the verify flow before settlement. |
| Has an authorized payment been settled? | Use the settle flow and retain the settlement receipt with payment logs. |
| What market data does the paid resource return? | Route back to OpenAPI, REST API, Schemas, and Data Quality. |
| Should the user get wallet-managed account keys? | Use Wallet Automation, then treat generated keys like ordinary API credentials. |
Market-Data Boundary
The x402 facilitator can protect a resource server that calls market data, but it does not change 0xArchive REST route taxonomy. A paid resource still needs correct venue family, symbol, schema, response parsing, data-quality behavior, and data-rights handling. If the user wants wallet-managed 0xArchive account keys, use Wallet Automation. If the user wants agent access, use Agentic Gateway. If the user wants normal market-data API calls, use Quickstart and Authentication.Why 0xArchive Fits
0xArchive separates payment infrastructure from market-data retrieval so a paid resource can settle payment without confusing the data contract. Builders can protect an API-backed resource with x402 while still using the same route families, response envelopes, request IDs, and freshness checks used by ordinary API clients.Implementation Checks
Check supported networks live
Confirm the exact network and scheme before configuring a resource server.
Set a clear paid resource
The server should name route, price, network, recipient, and response behavior.
Keep payment and data logs separate
Payment settlement receipts are not a substitute for market-data
meta.request_id.