Four surfaces. One verifiable data layer

PubFi product surfaces share public context, but only the installed Registry generation can establish an executable route

Use the surface that owns the current job

PubFi product surfaces share public context, but only the installed Registry generation can establish an executable route

Discovery

Compare public crypto data sources, documentation, coverage, commercial posture, and claim-safe status

Explore Discovery

Registry-backed API access

Inspect the live catalog and execute a selected exact route through the typed Rust gateway

Inspect the catalog

Hosted MCP

Use public capability tools, account-authenticated execution, or the separate accountless x402 endpoint

Open MCP discovery

Custom delivery

Scope source integration, packaging, service levels, and support for a specific production program

Discuss custom delivery

Product context is not runtime availability

PubFi product surfaces share public context, but only the installed Registry generation can establish an executable route

  1. Editorial pages explain fit

    Product and provider pages describe public use cases and source context. They do not promise a live PubFi route

  2. Registry detail proves the route contract

    Current execution requires a ready capability in the installed signed generation and matching Runtime OpenAPI

  3. Access stays route-specific

    Free, Credit, x402, unavailable, request, and response facts belong to the exact selected capability

Choose a surface, then verify the live contract

Get API key