# x402 Crypto Data API Source Fit | PubFi Discovery

> Track x402 and machine-payment readiness for crypto data source discovery without claiming PubFi executes live supplier payments.

Source: Discovery demand-led page records consumed by the public Discovery routes.
Format: text/markdown; charset=utf-8
Inclusion rule: public demand-led records must be indexable; draft/noindex records are not emitted as markdown pages.
Canonical SEO rule: the HTML page is the canonical SEO URL; this Markdown route is an agent-readable mirror.
Capability boundary: page existence does not imply PubFi publishes an MCP server, x402 payment route, autonomous supplier call, or supplier-payment execution flow.


URL: https://pubfi.ai/discovery/topic/x402-crypto-data-api
Markdown URL: https://pubfi.ai/discovery/topic/x402-crypto-data-api.md
Title: x402 Crypto Data API Source Fit
Summary: Track x402 and machine-payment readiness for crypto data source discovery without claiming PubFi executes live supplier payments.
Primary query: x402 crypto data API
Supporting queries: x402 API marketplace
Demand area: x402 crypto data APIs
Use case: Machine-payment source discovery
Best starting page: https://pubfi.ai/discovery/topic/x402-crypto-data-api
Availability status: request integration (Request integration)
Status-aware CTA: Signal x402 data demand
Actionability: not actionable
Status explanation: Discovery can compare x402 readiness and collect integration demand, but PubFi does not publish a payment endpoint, payment requirement, facilitator URL, asset/network allowlist, or supplier payment execution flow today.
Machine interest signal: x402 payment
Detail export status: public/featured-export
Related source pages:
- CoinGecko API: https://pubfi.ai/discovery/api/coingecko-api
- CoinMarketCap API: https://pubfi.ai/discovery/api/coinmarketcap-api
- Kaiko: https://pubfi.ai/discovery/api/kaiko
- Dune API: https://pubfi.ai/discovery/api/dune-api
Related category pages:
- Market data: https://pubfi.ai/discovery/category/market-data
- On-chain state: https://pubfi.ai/discovery/category/on-chain-state
Related chain pages: none
Source evidence:
- x402 protocol overview: https://www.x402.org/
- Coinbase x402 overview: https://docs.cdp.coinbase.com/x402/welcome
- Coinbase x402 Bazaar docs: https://docs.cdp.coinbase.com/x402/bazaar
- CoinGecko x402 docs: https://docs.coingecko.com/docs/x402
- CoinMarketCap x402 page: https://coinmarketcap.com/api/x402/
Comparison criteria:
- Pricing and payment terms: Compare whether price, amount, and refund or rate-limit caveats are public, returned by the 402 challenge, or still endpoint-specific.
- Chain, currency, and asset support: Check public support for networks and payment assets such as Base or USDC instead of assuming all wallets, chains, or currencies are accepted.
- Request signing and 402 flow: Look for the first 402 challenge, payment-required header or body, payment signature step, and final 200 data response before calling a source machine-payable.
- Endpoint coverage: Distinguish x402-enabled quote, listing, DEX, or marketplace endpoints from the broader provider catalog and from non-x402 market-data or on-chain-state sources.
- Human and agent callability: Prefer evidence that says whether developers, backend systems, wallets, or AI agents can call the endpoint and what spending controls are expected.
- PubFi payment boundary: Use this page for source discovery and integration interest; it does not claim PubFi executes x402 supplier payments or exposes a payment route today.
