Skip to main content
AnyAPI is a unified marketplace for scraping and data APIs. Reach hundreds of APIs through one interface and one key, pay per request in real US dollars, and let AnyAPI normalize the response schema and fail over automatically when a provider errors. No per-provider signups, no monthly plans, no juggling credentials. Top up a single wallet and start calling.

​
Build from the API contract

To pick a SKU by eye first, browse the catalog. Each platform has a page listing its endpoints, normalized schemas, and USD prices. Before you write a request, select the SKU and fetch its contract:
With MCP, call get_api for the selected SKU instead. Use only the fields declared in inputSchema. Input fields are SKU-specific, so do not add familiar names such as limit, cursor, page, or sort unless that schema declares them. If the API returns invalid_input, compare the request with the schema. Do not retry with guessed field names. If you are using a coding agent, give it the maintained AnyAPI integration instructions:

​
Why AnyAPI

One key, every API

A single AnyAPI key unlocks the whole catalog. Add an API to your app without creating yet another account.

Pay per request, in USD

No subscriptions. You’re billed the winning provider’s price in real dollars, and only when a call succeeds.

Normalized responses

Every API returns the same shape across providers, so your code doesn’t change when the upstream does.

Automatic failover

If a provider fails, AnyAPI retries the next one under the same request. Failed calls are never charged.

​
How it works

Every API is a single POST to /v1/run/{sku}: send the normalized input, get a normalized result.
1

Send a request

Call /v1/run/{sku} with the SKU’s normalized input and your API key.
2

AnyAPI routes it

We validate your input, then run it against the best provider — failing over to the next on error, all under one price reservation.
3

Get a normalized result

You receive { output, provider, costUsd, items }. You’re charged costUsd only on success.

​
Pricing

Pricing is pass-through in USD, surfaced as costUsd on every response. There are no subscriptions and no charge for failed calls — if every provider errors, you pay nothing. Most APIs are priced per result: a per-item rate for each result returned (a few also add a small base fee), so a call that returns 5 results costs less than one that returns 50. Some input schemas declare a result cap such as limit. Use that field only when the selected SKU’s inputSchema declares it. The response reports items, the count you were charged for. Catalog and get_api results carry nested pricing: pricing.from is the cheapest complete flat or linear offer, while pricing.failoverMaxUsd is the greatest fallback ceiling. Linear offers name their billable unit and include baseUsd, perUnitUsd, and maxUsd, so you can budget before making a call. Simple lookups are flat per request.

​
Every static price in two denominations

Every static discovery offer publishes its maximum twice: Lane-level pricing objects carry maxPer1kUsd too. Per 1,000 requests is the denomination AnyAPI quotes customers in. Most of the catalog costs a fraction of a cent per call, and per-request figures at that scale cannot be compared by eye. When you show a catalog price to a person, read maxPer1kUsd and label it /1k req - for example $96.60/1k req rather than $0.0966 per request. Read the published per-1k field instead of multiplying maxUsd yourself. AnyAPI derives it with exact fixed-point arithmetic, while a floating-point multiplication drifts: in most languages 0.0966 * 1000 is 96.60000000000001, and live catalog prices land on that case. baseUsd and perUnitUsd have no per-1k twin. They are charged per billable item inside a single call, so a per-1,000-request version of them would describe nothing you can be billed. Amounts that state what one specific call costs stay per request and are never scaled to 1,000: a price quote’s maxCostUsd and minCostUsd, the costUsd on a completed run, and your wallet balance. Report those exactly as returned.

​
For AI agents

If you are an AI agent (or are setting one up), AnyAPI’s whole catalog is available through one MCP server — no per-API integration needed:
  • Endpoint: https://api.getanyapi.com/mcp (Streamable HTTP)
  • Auth: Authorization: Bearer <ANYAPI_KEY> — required for run_api and get_balance; list_apis, search_apis, and get_api (discovery) work without a key.
  • Tools: search_apis → get_api → run_api. Find an API by keyword (or browse with list_apis), read its input JSON Schema, then execute it. Successful runs bill the wallet in USD (costUsd); failed runs are never charged. get_balance returns the wallet’s remaining USD.
See the MCP server page for per-client setup (Claude Code, Claude Desktop, Cursor, Codex) and the full tool reference. There is also an official agent skill (npx skills add getanyapi-com/skills) that teaches your agent this whole workflow, including pricing and error semantics. Agents can also use the plain REST surface — GET /v1/apis?category=... to browse, GET /catalog/search?q=... to search, and POST /v1/run/{sku} to execute — documented in the API Reference and machine-readable at the public /openapi.json.

​
Get started

Quickstart

Make your first call in under five minutes.

Connect over MCP

Give your AI agents the whole catalog through one MCP endpoint.

n8n community node

Run any AnyAPI endpoint inside an n8n workflow on one credential.

API Reference

Browse every API with typed request and response schemas.

Dashboard

Create keys, top up your wallet, and track usage.