Hundreds of scraping and data APIs through one gateway — one key, USD pay-per-request, normalized schemas, automatic failover.
Scored across 10 tools
Most tools target distinct stages of one workflow: list/search/get for catalog discovery, quote for pricing, run for execution, get_request for durable state, read_result for cached output. The only mild overlaps are list_apis vs search_apis and get_request vs read_result, but the descriptions clearly delineate scope (browse vs ranked search; stored request metadata vs reshaping a paid result). report_bug vs send_feedback is also explicitly partitioned by description.
Every tool follows a verb_noun snake_case pattern: get_api, get_balance, get_request, list_apis, quote_api, read_result, report_bug, run_api, search_apis, send_feedback. Verb choices are semantically meaningful and consistent (get/list/search for reads, quote/run for execution, report/send for feedback).
Ten tools map cleanly onto the gateway's lifecycle: discover (list/search/get), price (quote), execute (run), track (get_request), harvest (read_result), account (get_balance), and feedback (report_bug/send_feedback). Nothing appears redundant or missing at the count level.
The core marketplace loop—discover, quote, run, poll, read results, check balance—is fully covered with no dead ends. Minor gaps exist: no tool to list a user's past request history or usage/spend records, and no explicit cancel for queued/running requests.
Get the full definition of one API by API slug, including its normalized input/output JSON schemas, per-request and per-1,000-request USD pricing on every source, and nullable trailing-30-day latency p50/p95/p99 with the successful sample count. Latency percentiles describe observed successful requests; p99 is an observation, not a maximum or a client timeout guarantee. Entries with heavy:true produce large API responses.
Inputs: sku_id (required), context (required). Returns: scraper
Get the remaining wallet balance (in USD) for the AnyAPI key supplied as a Bearer token. Requires a valid AnyAPI key.
Inputs: context (required). Returns: balanceUsd
Inspect or resume a durable AnyAPI request by request_id. This reads AnyAPI's stored state and never repeats the paid provider dispatch. While status is queued or running, retryAfterSeconds gives the minimum interval between status checks.
Inputs: context (required), request_id (required). Returns: hint, note, error, items, +13 more
Browse available AnyAPI APIs as lightweight summaries (id, name, category, USD pricing), optionally filtered by category. Descriptions and schemas are omitted to keep catalog responses small. Each pricing offer carries both maxUsd (billed per request) and maxPer1kUsd (the same price per 1,000 requests).
Inputs: context (required), category. Returns: scrapers
Get the exact input-aware execution price for an API, free and without a key. Nothing is charged or executed. sku_id and input identify the proposed execution; pricing resolves exactly as it does for execution, and input validation can return invalid_input without a charge. Returns maxCostUsd (the ceiling reserved), minCostUsd (the likely charge), and the base/per-item breakdown explaining why they differ. These are USD amounts for this one call, not per-1,000-request catalog comparison rates.
Inputs: input (required), sku_id (required), context (required). Returns: exact, baseUsd, pricing, maxCostUsd, +3 more
Read or reshape a previously paid API result without executing or paying again. result_id identifies the full cached result; fields/max_items/summary/jq control its presentation, including row selection and slicing large fields. Results are cached ~15 min and are private to the authenticated account; an expired id returns result_expired.
Inputs: context (required), result_id (required), jq, fields, +2 more. Returns: hint, note, error, items, +13 more
Submit a defect report to AnyAPI about wrong, empty, or malformed API data for valid input, misleading or unactionable errors, incorrect prices or schemas, or retries that failed unexpectedly. Free, never charged. summary is required and contains one line; optional request_id identifies the stored request and its upstream error body without requiring the payload in the report.
Inputs: context (required), summary (required), sku, contact, +2 more. Returns: id, received
Execute an API by API slug with a normalized input payload. Every input schema is strict: unknown fields are rejected, not ignored, and field names can differ between related APIs. Inputs must conform to the endpoint's schema, not its description. Published latency p50/p95/p99 and sample counts describe observed successful requests; p99 is an observation, not a maximum or a client timeout guarantee. Requires a valid AnyAPI key as a Bearer token. Charges the USD wallet. Some failed wallet-funded requests incur processing charges passed through at cost, with no markup; the error message shows the amount charged. Results can be large. fields keeps selected keys, max_items caps returned rows, and summary returns an outline; these controls reduce response size without changing the charge. max_cost_usd caps what this one request may charge, in USD: sources priced above it are skipped, and when none fits the request is refused before it runs, with no charge.
Inputs: input (required), sku_id (required), context (required), jq, +4 more. Returns: hint, note, error, items, +13 more
Search APIs by meaning and keyword across name, slug, and description, returning matches with their descriptions but without schemas, ranked most relevant first. At least one of query, category, or platform is required, in any combination; category or platform without query enumerates that scope. limit caps matches (default 25, maximum 50). Each result carries a relevance score in (0,1] relative to the top match; a relevance floor drops weak matches, so total counts relevant matches before the limit. ranking identifies meaning-based ('semantic') or substring ('keyword') matching. Entries with heavy:true produce large API responses. Search results omit input schemas; API inputs require the endpoint's strict schema, whose field names can differ between related APIs.
Inputs: context (required), limit, query, category, +1 more. Returns: total, ranking, results
Submit non-defect feedback to AnyAPI about an API you could not find in the catalog, a missing result field, confusing documentation or tool descriptions, or an improvement that would make a task easier. Free, never charged. summary is required and contains one line; optional details describes the task or suggestion.
Inputs: context (required), summary (required), sku, contact, +2 more. Returns: id, received
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Add one secure layer between your agents and this server.