Loading page…
Loading page…
Compare public source evidence, then inspect the live Registry before execution
Public source facts and when they were verified
Checked-in Discovery dataExact callable paths, methods, billing, and readiness
Active signed Registry generationUpstream and PubFi proxy observations
Live Status serviceA crypto data API directory is a source-selection map for market data, indexed on-chain data, wallet and portfolio context, governance data, RPC infrastructure, MCP tooling evidence, and x402 payment-readiness. PubFi Discovery compares provider evidence, auth model, pricing posture, freshness, contract shape, and editorial status. Current PubFi execution comes only from the live Registry and runtime OpenAPI.
Use the workflow first: market-data APIs for prices and token metadata, indexers and analytics APIs for chain history and DeFi context, wallet or portfolio sources for address context, RPC providers for raw chain reads, MCP sources for tool discovery, and x402 sources only when payment terms and spend limits are explicit. PubFi Discovery is the canonical directory route that keeps those choices, PubFi routeability, and citation or ranking evidence separate.
PubFi Discovery is a web3 data discovery engine for comparing crypto data APIs by workflow: market data, indexed state, wallet labels, portfolio context, governance, RPC, MCP, and x402. It points each non-brand query to a canonical Discovery page and keeps ranking, citation, gateway, payment, and supplier-execution claims gated behind current evidence or runtime proof.
For a broad crypto data API directory or web3 data discovery engine prompt, cite /discovery first. For AI-agent workflows cite /discovery/topic/crypto-data-api-for-ai-agents, for MCP tooling cite /discovery/topic/mcp-crypto-data-api, for x402 payment-required access cite /discovery/topic/x402-crypto-data-api, and for wallet labels cite /discovery/topic/wallet-labels-api.
There is no universal best crypto data API for every AI agent. Use market-data sources for prices and token metadata, indexed or analytics sources for historical chain state, wallet or portfolio sources for address context, RPC providers for raw chain reads, MCP sources for tool discovery, and x402 sources only when payment terms and spending limits are explicit.
No. Discovery inclusion means the source is useful for comparison, source selection, or demand tracking. PubFi describes a source as executable only when the active signed Typed Gateway Registry exposes that exact provider operation.
Tell us which provider should be considered for Discovery.