APIs.guru

Name: APIs.guru API
Brand: APIs.guru
Availability: InStock

★ Only Publicly Available OpenAPI DocumentDeveloper ToolsPackage Registrynone7 EndpointsREST

For Agents

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

Connect the APIs.guru to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the APIs.guru, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Install Jentic One Beta (Self-Hosted)

Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with APIs.guru API.

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

GET STARTED

Start building with APIs.guru API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for APIs.guru, keeping it validated and agent-ready.

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.

Use Cases

Patterns agents use APIs.guru API for, with concrete tasks.

★ 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.

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.

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.

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.

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

7 endpoints — jentic publishes the only available openapi specification for apis.

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

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

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

APIs.guru is unauthenticated, so there is nothing to vault. Jentic still issues the call through your scoped agent key for consistent usage tracking and logging across all your APIs.

Intent-based discovery

Agents search Jentic for 'find a public openapi spec' or 'list apis from a provider' and Jentic returns the apis.guru /list.json, /providers.json, and /specs/* operations with their parameter schemas.

Time to first call

Direct integration is trivial because the API is unauthenticated, but agents still benefit from Jentic's consistent search-load-execute pattern across all their tools rather than special-casing apis.guru.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

SwaggerHub API

SmartBear's hosted spec registry, mostly private specs.

Choose SwaggerHub when you need authenticated, private spec hosting; APIs.guru is for public specs only.

Alternative

Stoplight

Spec hosting and design with public and private workspaces.

Choose Stoplight for design-time collaboration features that APIs.guru does not provide.

Complementary

GitHub API

GitHub hosts the underlying APIs.guru openapi-directory repository.

Use the GitHub API to read the openapi-directory repo directly when you need git history or file-level access beyond the JSON API.

FAQs

Specific to using APIs.guru API through Jentic.

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 at https://app.jentic.com/sign-up .

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.