the web api for ai agents
give your agent the web, on one key
web search, page reads, and instagram profiles from one api. we run the provider accounts, keys, and billing. you load prepaid credits and call.
{
"results": [
{
"title": "Qdrant",
"url": "https://qdrant.tech"
},
{
"title": "Weaviate",
"url": "https://weaviate.io"
}
]
}try it
fetch me one, no signup
tap an example and watch it fetch a real-shaped result. or try the one we can't (weather) to see an honest typed error.
POST /v1/search
tap an example →
no signup. tap an example and watch it fetch.
how it works
you bring one key. we bring the providers.
- 1
add one fetchbean key
call from curl or mcp. there are no provider accounts to open and no keys to rotate.
- 2
we route to the provider
we send each call to the right provider and manage its key, rate limits, and auth on our side.
- 3
you get a clean result
normalized json for the curated tools (or the raw provider response via run), metered against your prepaid credits.
why fetchbean
one integration, not a pile of keys.
no provider accounts to open
otherwise it's a separate provider per tool, each with its own signup, key, and dashboard. with fetchbean you sign up once.
one key, one bill
we hold the provider keys behind a single prepaid wallet. you stop rotating secrets across every project.
one stable shape
search, read, and instagram return the same json contract every time. your agent never parses a different schema per provider.
spend can't run past your balance
prepaid credits, not a card on file. when the balance runs out, calls stop.
capabilities
curated tools, normalized. raw access to the rest.
search
web search via Exa. query in, ranked results out, in a clean and stable shape your agent can rely on.
read
page content via Jina, with the boilerplate stripped out. billed by the tokens it uses.
instagram profile data via Tikhub, in one clean call.
need raw access to other search providers? run makes the call and passes the response back unchanged.
agent-native
made for tool loops, not dashboards
call it with plain curl, or drop the curated tools into your agent over our local mcp bridge. it works with any mcp client, including the claude agent sdk. a runaway loop can't drain a card, because the prepaid cap stops calls once credits run out, and provider failures cost zero. your agent learns one tool surface instead of a different provider api for every job.
pricing
prepaid credits. no surprise bills.
load credits and run your agent. when they run out, calls stop. there is no surprise invoice and no card to drain.
pay per call · provider failures & timeouts billed zero · reads metered by tokens
one key. skip the signups.
give your agent the web behind a single fetchbean key, on prepaid credits you can't overspend.