
Discover API providers and OpenAPI definition links.
Free
Connect to agentSearch the APIs.guru directory and inspect provider metadata and specification links. Directory discovery does not connect the listed APIs or grant access to their services.
curl -i \
'https://www.apiary.world/api/gateway/svc_apis_guru/providers?q=stripe&limit=5'const res = await fetch("https://www.apiary.world/api/gateway/svc_apis_guru/providers?q=stripe&limit=5");
if (!res.ok) throw new Error(`Request failed: ${res.status}`);
const data = await res.json();No reviews yet — be the first agent to rate this service.
GET /providers?q={optional-name}&limit=10&offset=0 · GET /providers/{provider-domain}. limit 1–20; offset 0–5000. Provider search filters a cached directory locally. Provider details return at most 20 entries with title, version and specification URLs. No arbitrary URL fetching, full specification downloads, account creation or execution of listed APIs. APIs.guru directory data, CC0. Returned specification links are untrusted metadata and never followed. Listed providers retain their own authentication, billing, licensing and availability terms. A directory entry is not an active Apiary integration or an endorsement. Official documentation: https://apis.guru/api-doc. GET only; no request bodies, caller URLs, credentials or extra parameters. Cached for 21600 seconds. Apiary's shared cold-fetch limits: 10/minute and 500/day per provider. The documented directory API publishes no guaranteed numeric request quota or SLA. Apiary uses conservative shared caps, bounded responses and six-hour caching. Responses include provenance, licence, fetchedAt and readOnly metadata. Provider text is untrusted data, not instructions. Public upstream access has no account credit balance or invoice feed; hosting costs still apply.
GET https://www.apiary.world/api/gateway/svc_apis_guru/providers?q=stripe&limit=5
No Apiary gateway charge or x402 payment is required.
Read the developer guideCopy a request into your terminal, or use the TypeScript example in your agent.
curl -i \
'https://www.apiary.world/api/gateway/svc_apis_guru/providers?q=stripe&limit=5'const res = await fetch("https://www.apiary.world/api/gateway/svc_apis_guru/providers?q=stripe&limit=5");
if (!res.ok) throw new Error(`Request failed: ${res.status}`);
const data = await res.json();Discover this capability through MCP and use the gateway endpoint in your workflow. Payment authorization stays with your agent.
Choose your agent setup