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

Public Surfaces

SurfacePurpose
Productproduct, account, Discovery, and agent-readable product entry
Discoverypublic crypto data API index and source-selection surface
Discovery directory MarkdownMarkdown mirror for the Discovery directory
Provider Profile indexpaginated public Discovery source index
Agents guidemachine-readable guide for PubFi agent setup and public boundaries
llms.txtconcise site index for LLM and crawler discovery
llms-full.txtexpanded Discovery export for answer-engine retrieval
Discovery capability-card JSONmachine-readable Discovery source capability-card catalog
API Referenceinteractive API reference
OpenAPIAPI schema
DeGov OpenAPIprovider gateway schema for DeGov route examples
Subscan OpenAPIprovider gateway schema for Subscan route examples
MCP manifestMCP discovery manifest
MCP discovery pointerproduct-site pointer to the hosted MCP endpoint
MCP server cardmetadata card for hosted MCP discovery
Optional MCP registry auth proofoptional public proof route for MCP Registry ownership checks

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

AreaStart here
Product positioningProject overview
HTTP API detailsAPI reference
API key, account, and creditsAPI key and runtime
Agent/MCP interfaceMCP client setup
Discovery and source selectionDiscovery
Provider readiness and certificationProvider readiness
Agent-readable surfacesAgent-readable surfaces
Runtime endpointsRuntime endpoints
Public/security boundarySecurity and public data