canonical: https://jentic.com/apis/apis.guru/apisguru-apis-guru

# Guru APIs.guru

Jentic publishes the only available OpenAPI specification for APIs.guru, keeping it validated and agent-ready. APIs.guru is the open Wikipedia-style directory of OpenAPI definitions for thousands of public APIs. Its read-only HTTP API exposes seven endpoints rooted at https://api.apis.guru/v2 that list providers, list APIs per provider, retrieve specific OpenAPI documents, and report repository metrics. It is the canonical place to discover well-known third-party API specs without scraping vendor sites and is widely used to seed catalogs, SDK generators, and code-completion tools.

## For AI agents

Discover thousands of public OpenAPI specs by browsing providers, APIs, services, and individual specs through 7 read-only endpoints.

## Scope

Does not host private specs, support write operations, or proxy live API calls - use for read-only discovery of public OpenAPI documents only.

## Capabilities

- List every API tracked by APIs.guru in one call to /list.json
- Read repository-wide metrics including totals and update frequency via /metrics.json
- List all providers with at least one API in the directory via /providers.json
- List the APIs published under a specific provider via /{provider}.json
- Retrieve a particular version of an API's OpenAPI document via `/specs/{provider}/{api}.json`
- Browse multi-service providers by serviceName via /{provider}/services.json and `/specs/{provider}/{service}/{api}.json`

## Use cases

### Seeding an internal API catalog

Populate an internal developer portal with thousands of public API specs by walking /providers.json, then /{provider}.json, then `/specs/{provider}/{api}.json` for each entry. The directory is openly available and updated frequently, so a nightly job keeps the catalog fresh without negotiating data feeds with each vendor. This is a much faster path to a comprehensive catalog than building scrapers per vendor.

Example prompt: GET /providers.json, then for each provider GET /{provider}.json and follow the swaggerUrl in each entry to download the spec.

### SDK generation across many APIs

Drive an SDK generator over a curated subset of APIs by reading /list.json, filtering by provider or category, and pulling each spec's URL with `/specs/{provider}/{api}.json.` Because APIs.guru normalises specs to OpenAPI, downstream generators do not need per-vendor adapters. This pattern underpins several open-source SDK and codegen projects that target tens of vendors at once.

Example prompt: GET /list.json, filter to a provider list, then GET `/specs/{provider}/{api}.json` for each and feed the response into your codegen pipeline.

### Spec discovery for AI tooling

Use APIs.guru to surface spec URLs to vector indexes, code-completion models, or catalog search engines without each tool having to track every vendor's documentation site. The /list.json output is a self-contained map of provider, version, and spec URL, ideal for periodic ingestion. This keeps tooling current as new vendors are added to the directory.

Example prompt: GET /list.json on a schedule, diff against the previous run, and ingest any new spec URLs into your AI tool's index.

### Agent-driven catalog discovery

An AI agent looking for the right public API to call can ask APIs.guru through Jentic for the provider list and specific specs, then load any retrieved spec into the agent's planner to answer the user's question. Because APIs.guru is read-only and unauthenticated, the agent does not need credentials and can move from discovery to action quickly.

Example prompt: Through Jentic, search 'find a public openapi spec', load apis.guru /list.json, and pick the provider whose description best matches the user's intent.

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/list.json` | List all APIs in the directory |
| GET | `/providers.json` | List all providers |
| GET | `/{provider}.json` | List APIs for a specific provider |
| GET | `/{provider}/services.json` | List serviceNames for a provider |
| GET | `/specs/{provider}/{api}.json` | Retrieve a specific API version |
| GET | `/specs/{provider}/{service}/{api}.json` | Retrieve a specific API version under a serviceName |
| GET | `/metrics.json` | Get repository metrics |

## Key resources

- **APIs** — List, browse, and retrieve public API specs through /list.json, /providers.json, /{provider}.json, and `/specs/{provider}/{api}.json.`

## Why Jentic

- **Setup:** Wiring the APIs.guru API by hand means learning its provider and spec listing shapes and paging the public directory yourself. Through Jentic you install once, import APIs.guru from the API Directory, and your agent calls it, no key to manage since the API is open.
- **Permission scoping:** APIs.guru is read-only over public OpenAPI documents, so scope the agent to the operations it needs, such as listing providers and fetching a spec, and leave out others unless you add them. You choose the allowed operations, so the agent only calls what you list.
- **Credential handling:** This API needs no credential, and any header your Jentic One instance does store is kept encrypted and injected at execution time. Nothing sensitive enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'find a public OpenAPI spec for a provider' or 'list known API providers', and Jentic returns the matching APIs.guru operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **SwaggerHub API** — SmartBear's hosted spec registry, mostly private specs.
- **Stoplight** — Spec hosting and design with public and private workspaces.
- **GitHub API** — GitHub hosts the underlying APIs.guru openapi-directory repository.

## FAQ

### Why is there no official OpenAPI spec for APIs.guru?

APIs.guru indexes other vendors' specs but does not historically publish its own OpenAPI document. Jentic generates and maintains this spec so that AI agents and developers can call APIs.guru via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer .

### What authentication does the APIs.guru API use?

None. The seven endpoints under https://api.apis.guru/v2 are open and unauthenticated, so calls work without credentials. Through Jentic the calls are issued via your scoped Jentic key for usage tracking, but no APIs.guru token is required.

### How do I find every API for a specific provider?

Call GET /{provider}.json with the provider domain, for example /googleapis.com.json. The response groups APIs by version and includes the swaggerUrl for each spec. For multi-service providers, use GET /{provider}/services.json first to enumerate serviceNames.

### How do I download a specific API spec through Jentic?

Search Jentic for 'find a public openapi spec', load the apis.guru `/specs/{provider}/{api}.json` operation, and execute with the provider domain and API version. Jentic returns the OpenAPI document as the response body.

### What are the rate limits for the APIs.guru API?

APIs.guru does not declare formal rate limits in the spec, but the project asks consumers to cache responses and pull /list.json periodically rather than per request. Mirror the JSON locally for production use rather than calling on the hot path.

### Can I limit what my agent is allowed to do with the APIs.guru API?

Yes. Because Jentic One is self-hosted, you decide which APIs.guru operations your agent may call, and it can only invoke the ones you list. The API is read-only over public OpenAPI documents, so you can allow just the operations you need, such as listing providers with /providers.json and fetching a spec with `/specs/{provider}/{api}.json`, while leaving others like /list.json or /metrics.json out. Any operation you do not add stays off limits to the agent.