Collection status
- Collected records
- 1290
- API product candidates
- 674
- Provider families
- 430
- Provider profiles
- 448
- Corpus categories
- 14
- Live DB read
- yes
- Public view
- growth_public_api_corpus_exports
- Gateway claim
- Not asserted by corpus
Find crypto data APIs for AI agents, MCP tooling evidence, x402 payment-readiness signals, apps, and analytics workflows without assuming every source is already routed through PubFi
Claim-safe statuses distinguish Provider Profiles, evaluation-only pages, requested integrations, and available gateway/tooling surfaces without exposing paid procurement, approval, or provider-fetching flows
Automated API growth writes public-safe docs and API metadata into the Supabase public corpus view, then exposes it here by provider, category, docs URL, auth, and commercial notes. Gateway execution remains unsupported until a separate adapter certification path says otherwise.
Profile evidence comes from public-safe collection-only metadata in the Supabase growth_public_api_corpus_exports view. It does not certify an adapter, assert PubFi gateway availability, create credentials, approve payments, or make a supplier API production-callable.
Collected candidate API metadata for 101 Blockchains; gateway support is not asserted by the corpus.
Collected candidate API metadata for 1F; gateway support is not asserted by the corpus.
Collected candidate API metadata for 1inch Business; gateway support is not asserted by the corpus.
Collected candidate API metadata for 1inch Business; gateway support is not asserted by the corpus.
Collected candidate API metadata for 1inch Business; gateway support is not asserted by the corpus.
Collected candidate API metadata for AccuKnox; gateway support is not asserted by the corpus.
Search by provider name or narrow the directory by chain, category, pricing model, and auth requirements before you open a provider profile.
Explorer and indexed Substrate chain API for accounts, extrinsics, governance, staking, and asset data
Official Polkadot, Kusama, and Substrate REST API for pre-aggregated ecosystem metrics
Indexing and query infrastructure for building custom blockchain data APIs across Substrate, EVM, and other networks
Decentralized indexing and query services for blockchain application data across Polkadot, Ethereum, and other ecosystems
Governance discussion, proposal, referendum, and vote context for Polkadot and Kusama communities
Managed RPC, archive node, and infrastructure services for Polkadot and other blockchain networks
Developer platform for Ethereum and multichain RPC, enhanced APIs, webhooks, and app infrastructure
Ethereum and multichain API infrastructure for RPC access, IPFS, and developer network services
RPC endpoint and blockchain infrastructure platform spanning Ethereum, Solana, and other networks
RPC and blockchain infrastructure network for developers needing multichain endpoint access
Managed blockchain nodes, RPC endpoints, and infrastructure tools for Web3 applications
Institutional blockchain node infrastructure, staking, wallet, and API services for enterprises
Use the paginated Provider Profile index for crawlable HTML links to every indexable profile, and use the API candidate directory for processed profile evidence.
Start with the source directory and filters, then use the status guides and provider-sourced evidence to decide whether to compare, verify, or request a route.
PubFi Discovery is a crypto data API directory for teams comparing on-chain state, RPC infrastructure, market data, MCP tooling evidence, x402 payment-readiness signals, and agent workflow source fit. It separates source selection, requestable integrations, and current PubFi availability without implying a live PubFi MCP server or x402 payment endpoint.
The status row above the directory tells you how complete a Provider Profile is. Use these claim-safe badges to understand whether PubFi is profiling, comparing, or documenting a callable route.
Cross-check the most decision-relevant claims against provider-owned docs, pricing pages, and public status sources before you route demand.
Use these supporting pages when the question is about machine workflows or payment/tooling posture rather than a single source profile.