--- title: "PubFi — Agent-native Crypto Data Layer" description: "Agent-native Crypto Data Layer with collected source discovery, a complete live capability catalog, and exact API proxy execution." canonical_url: "https://pubfi.ai/" --- # 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. Canonical HTML: https://pubfi.ai/ ## How PubFi works PubFi gives agents public source context, a live Registry-backed contract, and explicit access lanes. Each layer has one clear authority. 1. **Discover public sources.** 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. 2. **Inspect the live contract.** 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. 3. **Choose one access lane.** 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. 4. **Execute the exact route.** 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. ## When to use PubFi - **An agent must inspect before it calls:** Use PubFi when the client can enumerate the live catalog, read exact capability detail, and select a route from current evidence. - **A product needs one execution boundary:** Use PubFi when a team wants server-side provider credentials, typed route validation, bounded delivery, and account or x402 admission behind one Registry-backed gateway. - **Source discovery and execution must stay distinct:** Use PubFi when public source research is useful but runtime availability must remain fail-closed and independently verified. ## When not to use PubFi - **You need PubFi to choose the provider:** PubFi does not infer intent, rank capabilities, or select a route. The client agent owns that decision. - **You need one universal request or response schema:** Each capability keeps its exact route-specific request and response contract. PubFi does not flatten all providers into one schema. - **You need automatic supplier purchase or settlement:** PubFi accountless x402 is a seller-side payment lane for approved PubFi routes. It is not supplier procurement, wallet custody, or automatic provider payment. ## Access paths ### Public discovery and contracts - Cost: No account. - Authentication: No authentication is required for these read-only public resources. - Purpose: Read Discovery, the complete Registry capability catalog, exact capability detail, Runtime OpenAPI, and public MCP catalog tools. - Use this lane to find sources and inspect current executable contracts. - Public catalog access does not authorize route execution. - The live Registry, not checked-in marketing content, owns readiness. - Next: [Open Developers](https://pubfi.ai/developers). ### Registered account - Cost: Credits or account-bound :free. - Authentication: The selected credential must resolve to an admitted billing account. Exact :free variants remain account-bound and charge no Credit. - Purpose: Use a PubFi API key for HTTP execution or a PubFi API key or Supabase OAuth access token for protected hosted MCP tools. - Eligible billing accounts receive one lifetime starter grant of 1,000 Credits. Each starter allocation is valid for 365 days. - The current checked-in catalog defines 1,000 Credits for USD 1.00, valid for 365 days. - A purchase is available only when the authenticated billing response returns the exact current offer. Per-operation Credit cost comes from the live Registry. - Next: [Open app](https://pubfi.ai/login). ### Accountless x402 - Cost: Exact live route quote. - Authentication: Do not send a Bearer credential. The unsigned request receives an exact payment challenge, and the signed retry uses the environment-matched x402 lane. - Purpose: Use the explicit HTTP or MCP x402 endpoint for a route that the live Registry currently enables for accountless payment. - The live Registry, signed offer, pay-to address, asset, network, and payment challenge are authoritative. - x402 consumes no account Credits and creates no PubFi account, invoice, API key, or anonymous dashboard. - A published route can be unavailable, free, account-priced, or x402-priced. Do not infer a payment path from Discovery content. - Next: [Read the x402 guide](https://docs.pubfi.ai/getting-started/x402). ### Custom delivery - Cost: Custom terms. - Authentication: Access, commercial terms, and delivery boundaries are confirmed in writing for the selected program. - Purpose: Use a separately scoped delivery when a production program needs custom source integration, data packaging, service levels, or support. - Custom delivery does not make every indexed provider executable. - Source rights, credentials, route contracts, and acceptance stay explicit. - Contact PubFi with the workflow, data scope, and expected delivery requirements. - Next: [Discuss custom delivery](mailto:hello@pubfi.ai?subject=PubFi%20custom%20delivery). ## Public entry points - [About PubFi](https://pubfi.ai/about) - [Partners](https://pubfi.ai/partners) - [Contact PubFi](https://pubfi.ai/contact) - [Products](https://pubfi.ai/products) - [Developers](https://pubfi.ai/developers) - [Pricing and access](https://pubfi.ai/pricing) - [Agents guide](https://pubfi.ai/agents.md)