Prepaid, capped, auditable — for AI agents

One key. Every API your agent needs.

A fare card for your agent: one prepaid balance for everything it calls — called natively, under hard caps and a kill switch, with a receipt for every tap.

Give this to your agent — it takes it from there:

$read https://apifare.com/llms.txt and get yourself a key

Get a key How it works

Plugs into

Claude CodeCursorLibreChatOpenClawLangChainCrewAIn8n

What's on the key

Your agent can call

One prepaid balance pays for 1,500+ tools your agent can run today, 3,400+ more with your own key, every x402-native endpoint, search, filings, registries, weather, and anything you already hold a key for. There is no separate provider account or provider API key for eligible capabilities — one apifare account gives your agent a capped, auditable budget.

DSDataForSEOlive search · page fetch

APApifyready-to-run tools

SECSEC EDGARUS filings

CHCompanies HouseUK registry

OMOpen-Meteoweather

Brave Searchweb searchyour key

SBScrapingBeeweb scrapingyour key

OWOpenWeatherweatheryour key

falfal.aiAI inferenceyour key

402x402 endpointspay-per-call APIsrolling out

native proxy (provider's own API) your own keys (BYOK vault) 1,500+ ready-to-run tools (live once supply key lands) 3,400+ more with your own key x402-native endpoints — rolling out

Live means callable right now; rolling-out lanes light up here as they land. "Your key" runs on a key you vault (BYOK).

Exact per-call prices: /capabilities — the listed number is the number your balance is debited (CI-enforced).

How it works

Give it the key. It does the rest.

Anything that speaks MCP or plain HTTP — the agent discovers, calls, and pays on its own.

Your agent reads the keyread /llms.txt

one line in chat, the MCP server, or plain HTTP

It calls the provider natively/proxy/{provider}/…

the provider's own API, under your caps

One balance pays402 → top up → retry

every call lands on a signed, exportable audit chain

APIFARE

the fare an agent pays
sample receipt — fields exactly as issued

PAID

asked"verify Fastener Express Ltd"

providerdataforseo (native)

price0.3 credits

cap at time400 / day

remaining187.2 credits

when2026-09-05T09:12:44Z

sig 9f2ac31b6e…d417 · appended to the signed audit chain

The seatbelt

Your agent spends; you decide how much

Budget
prepaid credits; 402 with a top-up link when empty — or auto-refill, with your consent and ceilings
Per-agent capsdaily/monthly limits and allowlists per agent token, checked before dispatch
Kill switchstop any agent from your phone; effective on its very next call
Receiptsevery call, deny, kill, and payment on a signed, exportable audit chain

Install

Two ways in

For you

Your agent, your budget. The catalog is open under your caps.

Claude Code

claude mcp add apifare -e APIPAY_TOKEN=<token> -- npx -y apifare-mcp

Cursor

// .cursor/mcp.json
{"mcpServers":{"apifare":{"command":"npx","args":["-y","apifare-mcp"],"env":{"APIPAY_TOKEN":"<token>"}}}}

OpenClaw / ClawHub

clawhub install apifare

Get a key

For your users

Integrate once, free. Each user funds their own balance — you never touch the money. Live example: LibreChat, one YAML block, no code changes.

mcpServers:
  apifare:
    type: streamable-http
    url: https://apipay.fly.dev/mcp
    headers: { Authorization: "Bearer {{APIPAY_TOKEN}}" }

See the LibreChat integration

Pricing

Pay per call. Top up when you like.

$20

→ 2,000 credits (suggested). Roughly 6,666 live searches, or 20,000 weather calls, at listed prices.

→ 500 credits. Sign up and start with $5 of calls free (500 credits); 1 credit = $0.01.

Auto-refill

Consent once and the balance refills below your threshold — at most once a day, never past your monthly ceiling. Failed provider calls are refunded.

FAQ

Common questions

Do I need a separate account with each provider?

No — for eligible capabilities there is no separate provider account: one apifare key routes the call and your balance pays the listed price. For restricted platforms you vault your own key (BYOK) and apifare meters it at a flat 0.1 credit.

A provider call failed — am I charged?

No. Failed provider calls are refunded automatically as a compensating credit on the append-only ledger, referenced to the call id.

How is pricing structured?

Per call, in credits (1 credit = $0.01). The price listed on /capabilities is exactly what your balance is debited — CI fails our own build if page copy and billing ever drift.

Which agents and frameworks work?

Anything that speaks MCP or plain HTTP: Claude Code, Cursor, LibreChat, LangChain, CrewAI, n8n — or curl. Guides: integrations · llms.txt.

What stops my agent overspending?

Prepaid balance (hard stop at zero), per-agent daily/monthly caps and allowlists, a kill switch effective on the agent's next call, and a signed audit chain of every call, deny, and payment. Auto-refill only ever runs with your recorded consent, under your ceiling, and parks itself on any card failure.

How it runs

One human, a written constitution, and role agents operating the rest — support, canaries, rollbacks, this site's drafts. Money, legal posture, and public claims stay human; everything else ships itself, and the audit chain keeps score in public. Follow along: changelog · the weekly build-in-public digest.

Give your agent a budget.

Prepaid, capped, auditable — with a receipt for every tap.

Get a key Read llms.txt