fetchbean

fetchbean

The tools layer for AI agents. One key sits in front of many providers, so your agent can search the web, read pages, pull live data, and act on your own connected accounts without a separate signup, key, or bill for each. Clean JSON in, clean JSON out, over plain HTTP or MCP.

Why it exists

Every capability an agent needs 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, spanning 250+ tools across 30+ providers today.

How it works

• One key, many tools. Normalized endpoints for search, page reads, weather, social, and more return a stable JSON shape, plus a generic run for raw provider access.
• Connect your own accounts. Link GitHub, Slack, Linear, Notion, Stripe, Google Workspace, and more, so agents act on your data, not just public APIs. Your keys stay server-side, injected only at call time.
• Prepaid credits with a hard cap. Spend can never exceed your balance. Provider failures and timeouts are billed at zero.
• Agent-native MCP. The hosted MCP server exposes three tools (discover, describe, run) instead of dumping hundreds, so agents find the right tool, read its schema, then call it.
• Discovery without a key. Public endpoints and a machine-readable changelog let an agent find new and existing tools before it ever authenticates.

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