Skip to main content
fetchbean gives agents one API for search, page reading, weather, social data, connected work apps, and more. Managed operations use credentials fetchbean supplies; connected operations use a provider account you attach once. Calls use the same https://api.fetchbean.com base URL and your fb_ key. Provider failures and timeouts are billed at zero.

Quickstart

Create a key and make your first call.

Authentication

Learn how to pass your API key and handle auth errors.

Catalog

Every provider, endpoint, parameter, and per-call price.

MCP server

Point any MCP-compatible agent at the whole catalog through one connection.

How it works

Get started in three steps.
1

Get an API key

Sign in at fetchbean.com/app, open API Keys, and create a new key. Copy it immediately — it’s shown only once and starts with fb_.
2

Call a curated tool

Use a normalized endpoint like POST /v1/search to get a consistent JSON response regardless of which provider powers it under the hood:
3

Explore providers

Browse the Providers page, then use POST /v1/run to execute a registered catalog operation with a provider-specific response.

Your first call

All requests go to the base URL https://api.fetchbean.com. Here’s a search request you can run right now: