Discover APIs, inspect schemas and pricing, and call live data through ApiClay’s hosted MCP server. For apps and AI agents. Requires an ApiClay buyer API key as a bearer token. API calls may consume credits.
Scored across 3 tools
Each tool occupies a distinct stage of a clear workflow: search (discover vendors) → describe (inspect one vendor's routes/fields) → call (invoke an endpoint). There is no overlap in purpose, and the descriptions explicitly cross-reference each other (e.g. 'Use apiclay_describe_api first to get the parameters'), so misselection is very unlikely.
All three follow a consistent 'apiclay_verb_object' snake_case pattern with a shared server prefix. The only deviation is singular vs plural object naming (describe_api/call_api vs search_apis), which is a minor cosmetic inconsistency rather than a real ambiguity.
A generic API gateway needs exactly this trio—discovery, introspection, and execution—and each tool clearly earns its place. Nothing is redundant and the surface is small enough that an agent can reason about all three at once.
The core lifecycle (find vendor → learn schema → make the call) is fully covered, including parameter examples, pricing, and billing/refund semantics in the call tool. Gaps are minor and mostly outside the calling domain—there is no tool for inspecting account balance, usage history, or credit state, and no explicit pagination control for marketplace search.
Call /v1/api// through the ApiClay gateway with your account. Billing is the gateway's: the vendor's trial requests first, then your plan, then pay-as-you-go credits (calls through an ApiClay proxy never use trial or plan); failed calls are refunded. Returns status, content type, X-ApiClay-* headers and the body (parsed JSON, text up to 256 KB with a truncated flag, or base64 for binary; PNG/JPEG/GIF/WebP images also come as an image block). Use apiclay_describe_api first to get the parameters. vendor apiclay with path extract is ApiClay's own URL extraction (GET with query url and, in an X-Proxy-Config header, your own proxy or an ApiClay proxy choice, or POST with body {urls, output_mode, render_mode, ..., proxy} returning NDJSON; billed per extracted URL plus the browser and proxy fees it used).
Inputs: path (required), vendor (required), body, query, +2 more. Returns: body, path, error, method, +10 more
Show one vendor's API: each custom HTTP route, aggregator route or table with its method, path, public headers / query / body fields (types and required flags), delivery hints (render_mode, output_mode), request policy, pricing, and a ready-to-use apiclay_call_api argument example. Never shows private values or upstream details. Free; calls no API.
Inputs: vendor (required). Returns: tags, about, error, notes, +10 more
Search the ApiClay marketplace: public, approved APIs plus private APIs you own or administer. query matches the vendor username, title, short description, tags and category case-insensitively. Returns vendor usernames (for apiclay_describe_api and apiclay_call_api), titles, descriptions, category, tags, datasource type, pricing summary and route count. Free; calls no API.
Inputs: limit, query, category, datasource_type. Returns: count, error, query, results, +3 more
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.
