Get API access
Choose the API you want to use, then sign in and create one API key. The same key works across enabled PubFi routes.
- Choose API
- Create API key
- Start building
Free routes available · x402 on supported routes
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
Choose the API you want to use, then sign in and create one API key. The same key works across enabled PubFi routes.
Free routes available · x402 on supported routes
Describe your request in plain language. PubFi Discovery compares providers, coverage, access, and pricing for you.
I need wallet balances and transfers on Polkadot.
ChatGPT PluginComing soon · Under review
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
Production agents need to read on-chain activity, governance, and market context as conditions change, not after a team has stitched together another one-off integration.
x402 lets agents pay for data as part of the workflow. Data providers that do not expose agent-native access paths risk disappearing from the next generation of crypto products.
Every L2, Substrate chain, app-chain, and analytics vendor adds another source to evaluate. Discovery gives teams an open index for finding the right crypto data API before they route it into production.
Use Discovery to compare public crypto data sources, documentation, coverage, and access evidence. A Discovery record does not prove that PubFi can execute the source.
Read every capability page, then fetch exact capability detail or Runtime OpenAPI. The installed signed Registry generation owns current paths, methods, schemas, billing mode, and readiness.
Use public reads, an authenticated account, an explicit accountless x402 route, or a separately agreed custom delivery. Authentication and payment lanes do not fall back into each other.
Send the selected raw path and method. Request and response schemas stay route-specific, and a successful gateway call returns the validated provider response instead of one universal PubFi envelope.
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
Compare upstream Subscan and DeGov evidence for chain state, account activity, governance, and DAO freshness.
Shape structured context for narratives, governance, and market observability. Additional DeFi and market endpoints are coming soon.
Use scoped API keys for current PubFi routes and evaluate x402-capable provider evidence only when payment terms and runtime gates are explicit.
Use Discovery as the open index to find crypto data APIs, compare suppliers, and decide which routes to bring into PubFi.
PubFi is not just a bundle of endpoints. It is the data layer that helps agents and builders move from context to action with clear supplier routes
PubFi treats route planning, API-key scopes, and payment-readiness evidence as first-class, so agents can evaluate what is callable before any paid or supplier-specific flow is enabled.
PubFi combines production APIs, supplier routing, and custom delivery support so teams can treat crypto data as an operating layer instead of a pile of vendor contracts.
Discovery helps teams find any crypto data API, compare supplier fit, and route selected sources through PubFi when that is the right 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
Validate the data layer against one product surface or agent workflow.
Plan for machine-driven calls when governance, market, or chain events change.
Package supplier routing, backend delivery, and support around a production program.
Stop stitching crypto data,