# PubFi > PubFi turns available governance and chain data into agent-ready APIs today, adds Discovery as the open index for crypto data supply, and keeps DeFi, market, and execution workflows explicit as the roadmap expands. PubFi is the crypto data layer AI agents reach for when they need context. It packages 4 structured API surfaces covering Account & Chain Activity, DAO Intelligence, Real-Time Intelligence, Market Observability so products and agents can use them directly without building data pipelines first. Key facts: - Official site: https://pubfi.ai - Primary category: agent-native crypto data layer - API products (4): Subscan API, DeGov API, Insight API, DeFi API - Coverage areas: Account & Chain Activity, DAO Intelligence, Real-Time Intelligence, Market Observability - Main audience: AI agents, developers, crypto product teams, analysts, DAO tooling teams, DeFi monitoring teams, and solver or trading infrastructure teams - Core value: one integration, one bill, one schema for crypto context - Access models: API evaluation, Agent-triggered usage, Custom data supply-chain support - Partners: SNZ Capital, Web3 Foundation, Parity Technologies - Contact: hello@pubfi.ai ## Core Pages - [Homepage](https://pubfi.ai/): PubFi turns available governance and chain data into agent-ready APIs today, adds Discovery as the open index for crypto data supply, and keeps DeFi, market, and execution workflows explicit as the roadmap expands. Includes a public-safe gateway request and sanitized response example. - [Solution](https://pubfi.ai/#solution): PubFi packages the data and access patterns an agent or product needs to move from crypto context to action without building every data relationship from scratch. - [Why now](https://pubfi.ai/#why-now): Autonomous systems now have to monitor, decide, and act across fragmented chains. PubFi packages live context, route-readiness evidence, and discoverable supplier paths before that fragmentation becomes product debt. - [Partners](https://pubfi.ai/#partners): PubFi already serves 10,000+ users across 70+ chains, with backing from teams that have built, funded, and scaled crypto infrastructure. Current partners: SNZ Capital, Web3 Foundation, Parity Technologies. - [Plans](https://pubfi.ai/#plans): We are packaging agent-native access around request budgets, agent triggers, and custom delivery. Email hello@pubfi.ai for the current access path. Self-serve packaging is coming soon. For now, PubFi recommends an access path from your expected request budget, agent triggers, and data delivery scope. - [Contact](mailto:hello@pubfi.ai): Contact PubFi for API access, product questions, deployment planning, or custom backend collaboration. ## Blog Articles - [PubFi Blog](https://pubfi.ai/blog): Time-stamped technical notes, launch updates, and developer guides for crypto data APIs, Discovery, and agent workflows. - [How to Query Polkadot Ecosystem Governance Data with One PubFi API Key](https://pubfi.ai/blog/query-polkadot-governance-data-with-one-pubfi-api-key): Developer guides; Published June 8, 2026. A practical guide to combining Darwinia Subscan referenda reads with RingDAO DeGov activity as a Polkadot parachain governance example. - [PubFi Discovery: A Searchable Knowledge Layer for Crypto Data APIs](https://pubfi.ai/blog/pubfi-discovery-searchable-knowledge-layer-for-crypto-data-apis): PubFi Discovery; Published June 3, 2026. PubFi Discovery is a searchable knowledge layer for crypto data APIs, built for developers comparing source fit and agents retrieving capability boundaries before execution. ## Discovery - [PubFi Discovery](https://pubfi.ai/discovery): Public crypto API directory with provider, chain, category, capability, and commercial metadata. Current public machine-readable surface: 132 detail pages, 7 category hubs, 7 chain hubs, 5 comparison pages, and 7 demand-led pages. - [PubFi Discovery directory Markdown](https://pubfi.ai/discovery.md): Agent-readable Markdown mirror for the canonical crypto data API directory, non-brand query-to-page map, and source-selection boundaries. - [PubFi Discovery LLM export](https://pubfi.ai/llms-full.txt): Expanded Discovery export with publishable detail pages, category hubs, chain hubs, comparison pages, claim-safe CTA labels, commercial facts, demand-signal context, allowed Markdown detail URLs, and status-aware labels such as not_public, contact_sales, deprecated, conflicting, and plan-specific states. - [DotLake API Markdown detail](https://pubfi.ai/discovery/api/dotlake-api.md): Markdown mirror for the DotLake API detail page. Raw claim-safe status: public_source_profile. - [SubSquid Markdown detail](https://pubfi.ai/discovery/api/subsquid.md): Markdown mirror for the SubSquid detail page. Raw claim-safe status: public_source_profile. - [SubQuery Network Markdown detail](https://pubfi.ai/discovery/api/subquery.md): Markdown mirror for the SubQuery Network detail page. Raw claim-safe status: public_source_profile. - [Crypto Data API Directory For AI Agents Markdown detail](https://pubfi.ai/discovery/topic/crypto-data-api-for-ai-agents.md): Markdown mirror for the demand-led Discovery page that owns "crypto data API for AI agents". Availability status: Request integration. - [CoinGecko Alternatives for Crypto Data APIs Markdown detail](https://pubfi.ai/discovery/topic/coingecko-alternatives.md): Markdown mirror for the demand-led Discovery page that owns "CoinGecko alternatives". Availability status: Indexed-only. - [MCP Crypto Data API Directory For AI Agents Markdown detail](https://pubfi.ai/discovery/topic/mcp-crypto-data-api.md): Markdown mirror for the demand-led Discovery page that owns "MCP crypto data API". Availability status: Roadmap signal. - [x402 Crypto Data API Directory For AI Agents Markdown detail](https://pubfi.ai/discovery/topic/x402-crypto-data-api.md): Markdown mirror for the demand-led Discovery page that owns "x402 crypto data API". Availability status: Request integration. - [Polkadot Governance API Source Fit Markdown detail](https://pubfi.ai/discovery/topic/polkadot-governance-api.md): Markdown mirror for the demand-led Discovery page that owns "Polkadot governance API". Availability status: Request integration. - [Wallet Labels API Directory For AI Agents Markdown detail](https://pubfi.ai/discovery/topic/wallet-labels-api.md): Markdown mirror for the demand-led Discovery page that owns "wallet labels API". Availability status: Indexed-only. - [TypeScript Crypto Data API Directory For Developers Markdown detail](https://pubfi.ai/discovery/topic/typescript-crypto-data-api.md): Markdown mirror for the demand-led Discovery page that owns "TypeScript crypto data API". Availability status: Request integration. ## Agent-Readable Files - [PubFi public docs](https://docs.pubfi.ai): public. Public documentation for PubFi concepts, quickstarts, runtime boundaries, agent setup, examples, and claim-safety rules. - [Agents guide](https://pubfi.ai/agents.md): public. Markdown guide for agents using PubFi public docs, OpenAPI schemas, capability routes, and auth-required gateway routes. - [LLMs index](https://pubfi.ai/llms.txt): public. Concise index of public PubFi pages, documentation, Discovery exports, and integration resources. - [PubFi Discovery full export](https://pubfi.ai/llms-full.txt): public. Expanded Discovery export generated from checked-in public catalog records and publication gates. - [PubFi Discovery directory Markdown](https://pubfi.ai/discovery.md): public. Agent-readable Markdown mirror for the canonical crypto data API directory and non-brand query-to-page map. - [Discovery capability-card JSON](https://pubfi.ai/discovery/agent-capabilities.json): public. Discovery source capability cards with input schemas, normalized envelopes, provenance, and freshness metadata. - [PubFi Runtime OpenAPI](https://api.pubfi.ai/openapi.json): public. OpenAPI 3.1 schema for PubFi runtime HTTP routes, including capability, gateway, account, credit, usage, and MCP surfaces. Discovery export gates: - Directory Markdown URL: https://pubfi.ai/discovery.md - Markdown detail URL pattern: https://pubfi.ai/discovery/api/{source_slug}.md - Markdown detail links in this index are selected from indexable public Discovery detail records with readiness_flags.llms_export_ready=true. - Non-public measurement artifacts, local spool files, internal queues, and recommendation artifacts are not public LLM export sources. - Claim-safe status model: public_source_profile, evaluation_comparison_only, integration_requested, integration_planned, integration_in_progress, gateway_available, x402_available, mcp_tooling_available, unavailable_deferred. - Callable/tooling statuses: gateway_available, x402_available, mcp_tooling_available. Every other status is profile, comparison, demand, roadmap, or deferred context. - MCP manifest status: PubFi publishes a hosted MCP manifest at /.well-known/mcp.json for https://mcp.pubfi.ai with public handshake/introspection methods and authenticated tools/call execution; use /agents.md and OpenAPI schemas for current agent-readable setup. Discovery machine-native demand: - Agent data API guide: use https://pubfi.ai/discovery/topic/crypto-data-api-for-ai-agents for AI-agent crypto data source selection across market-data sources such as CoinGecko, CoinMarketCap, CoinAPI, and Kaiko; indexed, wallet, portfolio, governance, and DeFi sources such as The Graph, Bitquery, Chainbase, Subscan, Nansen, Zerion, and DefiLlama; RPC sources such as dRPC; and related MCP/x402 evidence by coverage, auth model, pricing posture, provenance, freshness evidence, contract surface, claim-safe status, and current PubFi availability. - Wallet labels API guide: use https://pubfi.ai/discovery/topic/wallet-labels-api for wallet-label and entity-intelligence source selection by separating wallet or portfolio sources such as Moralis and Zerion from entity-intelligence, holder, analytics, and indexed data sources such as Nansen, Allium, and Chainbase, plus compliance-oriented sources such as Scorechain. Treat source inclusion as Discovery evidence, not as a universal PubFi wallet-label gateway or regulated risk-decision claim. - MCP crypto data guide: use https://pubfi.ai/discovery/topic/mcp-crypto-data-api, provider Markdown mirrors, and this guide for MCP crypto data source selection by comparing hosted endpoint versus documented server shape, visible tools, auth, supported data families, official provider evidence, GitHub example boundaries, and read/write or payment limits; PubFi's public MCP materials describe generic route-tool boundaries; provider-specific crypto MCP tools and payment-requiring MCP data tools are outside this public guide unless separate runtime verification proves them. - x402 crypto data guide: use https://pubfi.ai/discovery/topic/x402-crypto-data-api for x402 crypto data source selection by comparing HTTP 402 challenge shape, payment amount and asset, supported network, signing or payment-proof step, endpoint family, final data response, rate-limit caveat, marketplace metadata, and agent spending boundary; CoinGecko and CoinMarketCap are market-data x402 evidence anchors, Coinbase Bazaar and x402.org are marketplace/protocol anchors, and PubFi does not publish a payment endpoint, payment requirement, facilitator URL, asset/network allowlist, or supplier payment execution flow today. - TypeScript crypto data API guide: use https://pubfi.ai/discovery/topic/typescript-crypto-data-api for TypeScript, curl, and server-side crypto data examples by choosing the source class before writing code: market-data APIs such as CoinGecko, CoinMarketCap, CoinAPI, and CryptoCompare; indexed or query APIs such as The Graph and Bitquery; and RPC infrastructure such as QuickNode and Chainstack. Keep provider keys server-side, use redacted example credentials, validate endpoint family and response shape with curl, and treat PubFi routeability as source-specific rather than implied by source inclusion. - Future demand-led Discovery pages or protocol-specific manifests should only appear when their public route, export, crawler, and claim-safe availability labels are defined from the same source records as the canonical Discovery pages. ## Developer Pages - [PubFi Docs](https://docs.pubfi.ai): Public documentation for PubFi concepts, quickstarts, runtime boundaries, agent setup, examples, and claim-safety rules. - [Agents guide](https://pubfi.ai/agents.md): Markdown guide for agents using PubFi public docs, OpenAPI schemas, hosted MCP, capability routes, auth-required gateway routes, and current x402 non-claim guidance. - [Capability discovery JSON](https://pubfi.ai/discovery/agent-capabilities.json): Contract-derived capability, input schema, normalized envelope, provenance, and freshness artifact for agents. - [PubFi Runtime OpenAPI](https://api.pubfi.ai/openapi.json): Machine-readable OpenAPI 3.1 schema for PubFi runtime HTTP routes, request bodies, response schemas, auth requirements, and route-level details. - [Gateway Quickstart](https://docs.pubfi.ai/getting-started/quickstart): Developer quickstart for PubFi API keys, gateway authentication, request headers, gateway routes, credits, and the current unified API contract. - [API Reference Guide](https://docs.pubfi.ai/reference/api-reference): Guide to PubFi's interactive API reference and OpenAPI schema for runtime HTTP methods, request bodies, response schemas, and auth requirements. - [Provider Gateway Examples](https://docs.pubfi.ai/reference/provider-gateway-examples): Public-safe Subscan, DeGov, and World Bank gateway route-shape examples, auth boundaries, common gateway outcomes, and provider-specific network placeholders. - [DeGov OpenAPI](https://pubfi.ai/openapi/degov-openapi.json): Machine-readable OpenAPI 3.1 schema for the PubFi DeGov gateway routes. Suitable for agents, tool registration, and API client generation. - [Subscan OpenAPI](https://pubfi.ai/openapi/subscan-openapi.json): Machine-readable OpenAPI 3.1 schema for the PubFi Subscan gateway routes. Suitable for agents, tool registration, and API client generation. OpenAPI schemas: - [PubFi Runtime OpenAPI](https://api.pubfi.ai/openapi.json): public. OpenAPI 3.1 schema for executable PubFi HTTP routes, request bodies, response schemas, auth requirements, and route-level details. - [DeGov OpenAPI](https://pubfi.ai/openapi/degov-openapi.json): public. OpenAPI 3.1 schema for DeGov gateway routes. Gateway calls require a PubFi API key. - [Subscan OpenAPI](https://pubfi.ai/openapi/subscan-openapi.json): public. OpenAPI 3.1 schema for Subscan gateway routes. Gateway calls require a PubFi API key. - Capability runtime rule: use /v1/capabilities/{capability_id} for repeated PubFi-native data calls when a v1 capability matches; provider gateway routes are lower-level implementation details. - Runtime OpenAPI rule: https://api.pubfi.ai/openapi.json covers executable PubFi HTTP route families; route discovery does not authorize live provider calls. ## Account Pages - [Log in](https://pubfi.ai/login): Auth-required email sign-in entry point for dashboard access, API billing context, and authenticated product usage. - Dashboard and account settings routes are authenticated account UI and are intentionally omitted from this agent-readable route list. ## API Products (4) - [Subscan API](https://pubfi.ai/products/subscan-api): Subscan API gives your app or agent a reliable way to read chain activity and account state across 70+ chains, including Polkadot, Kusama, Moonbeam, Midnight, and more, so you can ship user-facing crypto features without building core indexing first. Coverage: Substrate & EVM ecosystem explorer APIs, multichain beta resources, and selected EVM surfaces. Core data surfaces: accounts and balances, blocks and extrinsics, governance and staking, assets, tokens, and EVM data. Ideal for: Wallet, explorer, and portfolio experiences; Governance, staking, and account intelligence workflows; Agents that need dependable chain lookups before taking action. Agent skill integrations available for: PubFi Gateway. - [DeGov API](https://pubfi.ai/products/degov-api): DeGov API helps your product explain what is happening in a DAO and who is driving outcomes, making governance easier to monitor, analyze, and automate. Coverage: Cross-DAO governance coverage, DAO freshness metadata, and paid intelligence endpoint evidence. Core data surfaces: proposals, votes, delegates, treasury snapshots. Ideal for: Governance dashboards; Delegate intelligence and reporting products; DAO research agents and internal governance tooling. Agent skill integrations available for: PubFi Gateway. - [Insight API](https://pubfi.ai/products/insight-api): Insight API helps your users and agents catch important changes earlier by packaging live crypto narratives into streams they can monitor and act on. Coverage: Cross-source intelligence with real-time bias. Core data surfaces: topic streams, alerts, market context objects, narrative events. Ideal for: Intelligence dashboards; Real-time alerting; Analyst copilots and agent monitoring workflows. - [DeFi API](https://pubfi.ai/products/defi-api): DeFi API gives your users clearer market visibility faster, so you can build observability features without first designing the entire data model yourself. Coverage: Ethereum and Solana DeFi ecosystems. Core data surfaces: protocol metrics, wallet activity, token signals, dashboard feeds. Ideal for: Market observability products; Investment and strategy dashboards; Protocol monitoring and alerting workflows. ## Skill Install Guides - [Subscan API — PubFi Gateway](https://support.subscan.io/doc-362600): Install: `curl --location 'https://api.pubfi.ai/v1/gateway/subscan/polkadot/api/scan/account/tokens' \ --header 'Authorization: Bearer ' \ --header 'Content-Type: application/json' \ --data '{ "address": "" }'` — Recommended for product integration. Call the PubFi gateway with your own PubFi API key, and keep usage tracking unified in the dashboard. Guide: Subscan Conventions (https://support.subscan.io/doc-362600). - [DeGov API — PubFi Gateway](https://agent-api.degov.ai/v1/meta/pricing): Install: `curl --location 'https://api.pubfi.ai/v1/gateway/degov/global/v1/daos' \ --header 'Authorization: Bearer '` — Use the PubFi gateway route with the fixed `global` network segment for DeGov endpoints. Upstream x-degov-api-token auth stays server-side. Guide: Live pricing (https://agent-api.degov.ai/v1/meta/pricing). ## External Documentation - [Subscan API docs](https://support.subscan.io/doc-362600): External documentation for Subscan API. - [DeGov API docs](https://agent-api.degov.ai/v1/meta/pricing): External documentation for DeGov API. ## Optional - [Sitemap](https://pubfi.ai/sitemap.xml): XML sitemap for all public PubFi routes. - [Robots policy](https://pubfi.ai/robots.txt): Crawler policy with explicit allow rules for major AI search crawlers. - [LLMs index](https://pubfi.ai/llms.txt): Machine-readable index of PubFi pages, API products, documentation, and integration resources for LLMs and agents. - [Privacy Policy](https://pubfi.ai/privacy-policy): Legal privacy information for PubFi users. - [Terms of Service](https://pubfi.ai/terms-of-service): Legal terms for using PubFi services. ## Live Generic Gateway Catalog - Active generic release: billing-clean-cut-empty-1783840623 (b4e193fcf2957bd719dab4d6d3b72ee4c2583d2f144ffb98ca5e788ba1f06386). - Certification: validator pubfi-gateway-catalog-bootstrap:0.1.0:development; certified 2026-07-12T07:17:03Z; expires 2026-08-11T07:17:03Z.