← All Projects

fetchbean

One key, many providers | HTTP + hosted MCP

One API key for the web tools agents need: search, page reads, weather, social data, and more. fetchbean runs the provider accounts, keys, and billing; you load prepaid credits you can't overspend and call.

By Aman Kumar • 2026-06-17

TypeScript
Hono
Bun
PostgreSQL
MCP
Cloudflare Workers
fetchbean

fetchbean

The web API for AI agents. One key sits in front of many web-tool providers, so you don't open a separate account, manage a separate key, or track a separate bill for each one. Clean JSON in, clean JSON out, over plain HTTP or MCP.

Why it exists

Agents need to search the web, read pages, pull social data, and check the weather. Each capability normally means its own provider signup, API key, rate limit, and invoice. fetchbean collapses that into a single key and a single prepaid wallet you can't overspend.

How it works

  • One key, many tools. Curated, normalized endpoints (search, read, weather, and more) return a stable JSON shape, plus a generic run for raw provider access.
  • Prepaid credits with a hard cap. Spend can never exceed your balance. Provider failures and timeouts are billed at zero.
  • HTTP or MCP. Call it with curl, or connect the hosted MCP server to any agent (Claude, Cursor, the Agent SDK).
  • Discovery without a key. Public endpoints let an agent find which tool to use before it ever authenticates.

Built on Hono and Bun with a Postgres reserve-then-settle billing engine. Docs at docs.fetchbean.com.

AIAPIAgentInfrastructure