Calling provider operations through one fetchbean endpoint

fetchbean fronts a growing set of providers for web search, page reading, weather, social data, connected work apps, and more. POST /v1/run executes operations registered in the fetchbean catalog. It validates the input, supplies a managed or connected credential as required, and returns the operation’s provider-specific result without applying a provider-independent normalization layer.

The run interface

The POST /v1/run request body accepts these fields. provider and endpoint are required; input defaults to an empty object.

Field	Type	Description
`provider`	string	The provider identifier — for example `exa`, `jina`, `parallel`, `brave`, `openweather`, or `remoteok`.
`endpoint`	string	The endpoint coordinate registered for the operation, for example `/search` or `/v1/extract`.
`input`	object	Input validated against the registered operation’s JSON Schema.

Each method has a defined set of accepted parameters and a per-call credit cost. Refer to the full catalog for every supported provider, endpoint, and its pricing.

Examples

Use the tabs below to see how to call different providers through the unified run endpoint.

curl https://api.fetchbean.com/v1/run \
  -H "X-API-Key: $FETCHBEAN_KEY" \
  -H "Content-Type: application/json" \
  -d '{"provider":"exa","endpoint":"/search","input":{"query":"best vector databases","numResults":10}}'

curl https://api.fetchbean.com/v1/run \
  -H "X-API-Key: $FETCHBEAN_KEY" \
  -H "Content-Type: application/json" \
  -d '{"provider":"jina","endpoint":"/read","input":{"url":"https://example.com/post"}}'

curl https://api.fetchbean.com/v1/run \
  -H "X-API-Key: $FETCHBEAN_KEY" \
  -H "Content-Type: application/json" \
  -d '{"provider":"parallel","endpoint":"/v1/search","input":{"search_queries":["vector databases"]}}'

curl https://api.fetchbean.com/v1/run \
  -H "X-API-Key: $FETCHBEAN_KEY" \
  -H "Content-Type: application/json" \
  -d '{"provider":"parallel","endpoint":"/v1/extract","input":{"urls":["https://example.com"]}}'

Normalized shortcuts

Every named tool also has its own endpoint at POST /v1/<name>, so you can call it without assembling a provider and endpoint pair. The same registered operation is reachable through POST /v1/run.

Five of those endpoints are provider-independent: fetchbean picks the provider and normalizes the response, so the shape stays stable even if the provider behind it changes.

POST /v1/search — web search with a uniform result schema.
POST /v1/read — page reading with a consistent content structure.
POST /v1/weather — current weather data in a standardized format.
POST /v1/ios_app_search — iOS App Store search.

The rest are named after the provider they call (POST /v1/linear_issues, POST /v1/stripe_charges, and so on) and return that operation’s provider-specific result. See the curated tools guide for the full picture.

Browse every provider, method, parameter set, and per-call credit cost at fetchbean.com/catalog.

Get Started

Core Concepts

Guides

Reference

Calling provider operations through one fetchbean endpoint

The run interface

Examples

Normalized shortcuts

​The run interface

​Examples

​Normalized shortcuts

The run interface

Examples

Normalized shortcuts