Facilitator Model
Public Endpoint Roles
Use the live facilitator page for current endpoint behavior and network state. Do not hard-code network availability from stale docs when the facilitator endpoint can be checked live.
Payment Boundary Checklist
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.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 needs existing-wallet account verification, use SIWE verification. If the user needs new paid wallet access, use the x402 subscription flow on that page. 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
1
Check networks live
Confirm the exact network and scheme before configuring a resource server.
2
Set a clear paid resource
The server should name route, price, network, recipient, and response behavior.
3
Keep payment and data logs separate
Payment settlement receipts are not a substitute for market-data
meta.request_id.4
Preserve data boundaries
x402 payment does not grant raw-data redistribution rights or bypass data-quality checks.