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

​
Start Here

  1. Read the Project Overview to understand PubFi’s product boundary.
  2. Use the Quickstart to choose an interface and execution lane.
  3. Use the Staging Guide before you test an integration.

​
Choose Your Path

Explore concrete journeys through Crypto API Discovery, Source Evaluation, Provider Integration Review, Agent And Answer-Engine Discovery, and Agent Wallet Balance.

​
Contract Authority

Use current runtime surfaces instead of saved routes or inferred provider URLs: Use Public Surfaces for the complete human-facing URL inventory. Use Agent-Readable Surfaces for machine-consumable indexes and authority order.

​
Core Boundary

Discovery inclusion does not mean gateway availability. A route plan does not authorize execution. The installed Registry and request-time gates determine whether a route can run. Staging permits Base Sepolia eip155:84532 for eligible x402 tests. Production permits Base mainnet eip155:8453 only when x402 is enabled for the exact route. Environment policy does not prove current route or offer availability.