One key for every API
Key sprawl is the quiet tax on agent systems: a provider account, a billing relationship and a leaked-secret surface for every capability.
One key instead
apifare gives your agent one bearer token. Behind it:
- Ready-to-run tools. Search, page fetch, filings, registries, weather and the ready-to-run tools in the tool catalog, with no separate provider account or provider API key.
- Your own keys, vaulted. Tools that run on your own provider account work too. Vault the key once through a one-time link; it is injected server-side and never shown to the agent.
- Native provider APIs. Call a provider's own API shape through
/proxy/{provider}/{path}, with your vaulted key injected server-side. - x402 endpoints. Rolling out.
Find what's callable
Your agent searches everything with GET /v1/search?q=…; results carry their lane and listed price. People can browse the tool catalog and the API guides.
The rule that keeps it honest
The listed per-call price is what the balance is debited: one source of truth, CI-enforced. Exact numbers are on /capabilities.
Set it up
Get a key at /start (email in, token out, shown once), then connect your agent with its integration guide. The full reference is in the docs.
More guides
Give your agent a budget · Scrapers and data tools under hard caps · Docs