fetchbean

fetchbean

The tools layer for AI agents. One fetchbean key calls managed web tools, live data, and connected work apps through the same interface. Managed tools are ready to call; tools that act on your data use an account you connect once. JSON in and out, over plain HTTP or MCP.

Why it exists

Adding another agent capability often brings another provider, credential, response shape, and bill. fetchbean puts 1,000+ tools across ~100 providers behind one calling convention and one prepaid wallet.

How it works

• One key, many tools. Provider-independent endpoints normalize common tasks. Named tools and run execute operations listed in the catalog.
• Connect your own accounts. Link GitHub, Slack, Linear, Notion, Stripe, Google Workspace, and more, so agents act on your data, not just public APIs. Provider credentials stay server-side and are sent only to that provider.
• Prepaid credits. Each tool shows its fixed price or metered pricing model before the call. Provider failures and timeouts are billed at zero.
• Agent-native MCP. The hosted MCP server exposes four tools (discover, describe, run, and request) instead of loading the catalog into context, so agents find the right tool, inspect 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.