---
title: "About PubFi"
description: "Learn how PubFi separates crypto data discovery, live Registry contracts, exact execution, and explicit account or x402 access lanes."
canonical_url: "https://pubfi.ai/about"
---

# A crypto data layer agents can inspect before they execute

> PubFi helps agents and product teams discover crypto data sources, inspect current executable contracts, and call selected routes through one controlled gateway boundary.

Canonical HTML: https://pubfi.ai/about

## One platform with separate evidence and execution layers

PubFi keeps public source research, runtime availability, and payment authority distinct.

### 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.

### 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.

### 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.

### 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.

## Teams that need current crypto data contracts

### AI agent builders

Enumerate current capabilities, inspect exact schemas, and let the client agent select the route.

### Crypto product teams

Use one controlled execution boundary without moving provider credentials into browsers or agents.

### Data and ecosystem teams

Make public source evidence easier to find while keeping integration review and live readiness separate.

## 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.

## Continue

- [See how it works](https://pubfi.ai/#how-pubfi-works)
- [Open Developers](https://pubfi.ai/developers)