PubFi Docs

PubFi is building an agent-native crypto data layer. It helps software teams and AI agents discover crypto data sources, plan routes, inspect schemas, and use normalized capability contracts without binding every workflow directly to a different upstream API.

​

What To Read First

• Project overview: what PubFi is and what it is not.
• Quickstart: the shortest path through public docs and live surfaces.
• API reference: where to find the interactive HTTP reference and OpenAPI schema.
• API key and runtime: how billing accounts, request allowance, usage, and runtime boundaries fit together.
• MCP client setup: connect an agent runtime to PubFi’s generic MCP tools.
• Discovery: understand the public source-selection layer.
• Capability contracts: understand normalized agent-facing responses.
• Agent-readable surfaces: understand llms.txt, llms-full.txt, OpenAPI, MCP, and Discovery links.

​

Public Surfaces

​

Claim Boundary

Discovery inclusion does not mean gateway availability. A route plan does not authorize execution. Local SEO/GEO evidence does not prove ranking, traffic, or AI citation success. PubFi keeps those boundaries explicit so agents can choose routes safely.

​

Coverage Map