PubFi
My APIs

Choose the access path that matches the request

PubFi has public read-only resources, registered-account execution, explicit accountless x402 routes, and custom delivery. Current route and purchase availability come from live authority

Compare the boundary, not a fixed tier

Public, registered-account, accountless x402, and custom delivery answer different authentication, billing, and delivery needs

  1. Public discovery and contracts

    Read Discovery, the complete Registry capability catalog, exact capability detail, Runtime OpenAPI, and public MCP catalog tools.

    Access boundary
    No authentication is required for these read-only public resources.
    Path details
    • Use this lane to find sources and inspect current executable contracts.
    • Public catalog access does not authorize route execution.
    • The live Registry, not checked-in marketing content, owns readiness.
    Open Developers

  2. Registered account

    Use a PubFi API key for HTTP execution or a PubFi API key or Supabase OAuth access token for protected hosted MCP tools.

    Access boundary
    The selected credential must resolve to an admitted billing account. Exact :free variants remain account-bound and charge no Credit.
    Path details
    • Eligible billing accounts receive one lifetime starter grant of 1,000 Credits. Each starter allocation is valid for 365 days.
    • The current checked-in catalog defines 1,000 Credits for USD 1.00, valid for 365 days.
    • A purchase is available only when the authenticated billing response returns the exact current offer. Per-operation Credit cost comes from the live Registry.
    Get API key

  3. Accountless x402

    Use the explicit HTTP or MCP x402 endpoint for a route that the live Registry currently enables for accountless payment.

    Access boundary
    Do not send a Bearer credential. The unsigned request receives an exact payment challenge, and the signed retry uses the environment-matched x402 lane.
    Path details
    • The live Registry, signed offer, pay-to address, asset, network, and payment challenge are authoritative.
    • x402 consumes no account Credits and creates no PubFi account, invoice, API key, or anonymous dashboard.
    • A published route can be unavailable, free, account-priced, or x402-priced. Do not infer a payment path from Discovery content.
    Read the x402 guide

  4. Custom delivery

    Use a separately scoped delivery when a production program needs custom source integration, data packaging, service levels, or support.

    Access boundary
    Access, commercial terms, and delivery boundaries are confirmed in writing for the selected program.
    Path details
    • Custom delivery does not make every indexed provider executable.
    • Source rights, credentials, route contracts, and acceptance stay explicit.
    • Contact PubFi with the workflow, data scope, and expected delivery requirements.
    Discuss custom delivery

Choose by execution and billing need

Inspect before integration

Start with public catalog, capability detail, and Runtime OpenAPI reads. These show current contracts without authorizing execution.

Use an account for repeat workloads

Use account credentials when a product needs account-bound free variants, Credit-funded operations, dashboard history, or hosted MCP OAuth.

Use x402 for an eligible accountless call

Use x402 only when the exact live route publishes that lane and the caller can validate and enforce the payment challenge.

Scope custom delivery separately

Use custom delivery when source integration, packaging, service levels, or support must be agreed for a production program.

Access and pricing FAQ

Does every PubFi route cost one Credit?

No. Exact route variants can be public reads, account-bound free operations, Credit-priced account operations, unavailable for pricing, or explicitly enabled for x402. Inspect live capability detail before each integration.

Is the checked-in Credit purchase always available?

No. The checked-in catalog defines the accepted product identity. The dashboard shows a purchase only when the authenticated Quantro billing response returns the exact current offer and terms.

Does x402 use my PubFi Credit balance?

No. Accountless x402 is a separate cash lane. It does not create or consume account Credits and does not create an account invoice or dashboard.

Do all providers use one request and response schema?

No. PubFi keeps exact route-specific schemas. The installed Registry and Runtime OpenAPI publish the current contract for each capability.

When should I contact PubFi?

Contact PubFi when the live self-serve paths do not cover the required source, delivery scope, service level, or production support boundary.