x402 facilitator

The 0xArchive x402 facilitator verifies and settles exact EVM payments for x402 resource servers, on the networks it lists live. Use it when you run a paid resource and need payments checked and settled. Market-data requests still authenticate with your API key, and a paid resource that serves market data keeps the same routes, responses, request IDs, and freshness checks as any other client.

How the pieces fit

Layer	Role
The facilitator	Verifies and settles exact EVM payment data
Your resource server	Defines the paid routes, accepted networks, price, and recipient
The client signer	Signs the exact payment authorization
The 0xArchive market-data API	An optional resource behind your server, with its own route and response contract

Endpoints

Endpoint	Use
`GET https://facilitator.0xarchive.io/supported`	The networks and schemes available now
`POST https://facilitator.0xarchive.io/verify`	Check payment data before settlement
`POST https://facilitator.0xarchive.io/settle`	Submit an authorized payment for settlement
`GET https://facilitator.0xarchive.io/health`	Facilitator liveness

Read the live supported networks and schemes before configuring a resource rather than relying on a list in any document. The x402 facilitator overview describes the payment protocol.

Set up a paid resource

Check networks live

Confirm the exact network and scheme from /supported before configuring the resource server.

Define the paid resource

Set the route, price, network, recipient, and response behavior on your server.

Verify, then settle

Verify the signed authorization, then settle it, and keep the settlement receipt with your payment logs.

Keep payment and data logs separate

A settlement receipt does not replace the market-data meta.request_id. Log both.

Keep the data terms

An x402 payment does not grant raw-data redistribution rights or bypass data-quality checks.

Where each question goes

Question	Go to
Which networks and schemes can I use now?	`GET https://facilitator.0xarchive.io/supported`
Did the client sign an exact payment authorization?	The verify flow, before settlement
Has an authorized payment settled?	The settle flow; keep the receipt with payment logs
What market data does the paid resource return?	OpenAPI, the REST API, Schemas, and Data quality
Should an existing wallet confirm ownership for account or key management?	SIWE verification; new wallet-only access uses the paid x402 path on the same page
Should an agent call market data?	Coding agents
Do I just need ordinary API calls?	Quickstart and Authentication

Next step

Pay for an 0xArchive plan from a wallet with the x402 path in Wallet access and SIWE verification.

SDKs

CLI

MCP

Agent skill

AI agents

How the pieces fit

Endpoints

Set up a paid resource

Where each question goes

Next step

​How the pieces fit

​Endpoints

​Set up a paid resource

​Where each question goes

​Next step

How the pieces fit

Endpoints

Set up a paid resource

Where each question goes

Next step