Guru APIs.guru
70
AI ReadinessAI-Aware (A-)70/100
Community OpenAPI document · agent-readyDeveloper ToolsPackage Registrynone7 EndpointsREST
Know of an official OpenAPI document? Contribute it →
For Agents
Lets an AI agent browse the APIs.guru directory and fetch OpenAPI definitions for a given provider and API without authentication.
Use for: I need the OpenAPI definition for a specific provider's API, List all APIs tracked in the APIs.guru directory, Find which providers publish APIs in the directory, Get the services published under a given provider
Not supported: Serves the APIs.guru directory of API definitions only; it does not host, edit, or validate your own specs, so pair it with a design tool for those tasks.
APIs.guru is a directory of machine-readable API definitions, and its REST API serves that catalogue over HTTP. It lists every tracked API and provider, returns catalogue metrics, and fetches the OpenAPI definition for a given provider and service. The service is open and needs no authentication.
Install Jentic One Beta
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.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fapis.guru%2Fapis-guru" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fapis.guru%2Fapis-guru" | sh
jentic register # connects your agent to your Jentic One instanceJentic 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 in the APIs.guru directory
List the providers that publish tracked APIs
Return catalogue-wide metrics about the directory
Fetch the OpenAPI definition for a given provider and API
List the services published under a single provider
Use Cases
Patterns agents use APIs.guru API for, with concrete tasks.
★ Discover API specifications programmatically
Tools that work with many APIs need a source of specifications. The APIs.guru API lists every tracked API and provider and fetches an OpenAPI definition on demand, so an integration can find and pull the spec it needs without scraping vendor sites.
Fetch the OpenAPI definition for a named provider and API and return it.
Feed a catalogue of APIs into tooling
Documentation portals and testing tools ingest large sets of API definitions. The API returns the full list of tracked APIs and providers along with catalogue metrics, so a portal can enumerate what is available and refresh its own index.
List the tracked APIs and report how many the directory currently holds.
Look up a provider's services
A single provider may publish several APIs. The API returns the services under a provider and the definition for each, so an integration can drill from a provider name down to the exact spec it wants.
List the services a given provider publishes and fetch one definition.
Let an agent find and read API specs
An AI agent that integrates with third-party APIs can locate a specification itself. Through Jentic the agent discovers the directory operations by intent and runs them, returning the OpenAPI definition for the provider and API the user named.
Given a provider and API name, fetch and return its OpenAPI definition.
Key Endpoints
7 endpoints — apis.
METHOD
PATH
DESCRIPTION
GET
/list.json
List every API tracked in the directory
GET
/providers.json
List the providers in the directory
GET
/metrics.json
Return catalogue-wide directory metrics
GET
/{provider}.json
List a provider's tracked APIs
GET
/specs/{provider}/{api}.json
Fetch the OpenAPI definition for a provider and API
GET
/list.json
List every API tracked in the directory
GET
/providers.json
List the providers in the directory
GET
/metrics.json
Return catalogue-wide directory metrics
GET
/{provider}.json
List a provider's tracked APIs
GET
/specs/{provider}/{api}.json
Fetch the OpenAPI definition for a provider and API
Jentic AI Readiness Score
This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.
A
APIs.guru
- AI-Aware (A-)70/100
90
Foundational Compliance49
Developer Experience & Jentic Compatibility54
AI-Readiness & Agent Experience94
Agent Usability100
Security100
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
90
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: ASignals: 4
99%
Lint Results
Aggregated quality score from linter diagnostics, weighted by severity.
100%
Resolution Completeness
Percentage of `$ref` references that resolve successfully.
100%
Specification Validity
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
60%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
49
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: D+Signals: 4
10%
Example Density
How richly the API is illustrated with examples.
60%
Example Validity
Percentage of examples that conform to their schemas.
25%
Response Coverage
Percentage of operations with complete response definitions (success, client error, server error).
100%
Tooling Readiness
Health of API ingestion, bundling, and resolution within Jentic pipelines.
54
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: CSignals: 4
67%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
100%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
50%
Summary Coverage
Coverage of summaries across operations/tags/info.
94
Agent Usability
Functional utility, complexity comfort, and AI orchestration readiness.
Grade: A+Signals: 1
94%
Complexity Comfort
Agent comfort level based on API operational and structural complexity.
100
Security
Trust, risk posture, and security compliance.
Grade: A+Signals: 1
100%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
100
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: A+Signals: 1
100%
Descriptive Richness
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Pulling the APIs.guru catalogue yourself means calling several endpoints and stitching the provider and API records together. With Jentic you install once, import APIs.guru from the Directory, and start querying the catalogue right away.
Permission scoping
Running Jentic in your own instance, you decide which APIs.guru operations the agent may call, so you can allow catalogue reads while keeping the surface narrow. Access is granted per operation.
Credential isolation
APIs.guru is a public catalogue that needs no API key, so there is nothing to hold or inject. Every call still runs from your own self-hosted Jentic instance, under your own logging and controls.
Intent-based discovery
Agents find APIs.guru through Jentic's intent search: a request like fetch a provider's OpenAPI definition resolves to the right operation with its inputs prepared.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using APIs.guru API through Jentic.
Is there an MCP server for the APIs.guru API?
You do not need a dedicated MCP server. Through Jentic your self-hosted agent can call APIs.guru operations directly by intent, so you connect the API without maintaining separate MCP tooling.
Can I control which APIs.guru operations my agent calls?
Yes. Because you run Jentic yourself, you choose which APIs.guru operations your agent can call, so you can allow catalogue reads while withholding anything you would rather keep off. Scoping is applied per operation.
Does the APIs.guru API require authentication?
No. The APIs.guru directory is public and needs no API key, so calls run without authentication. Jentic still routes every request through your own self-hosted instance and controls.
What does a definition lookup return?
A lookup returns the OpenAPI definition for a given provider and API, so you can read its endpoints, schemas, and metadata directly from the directory.
How current is the APIs.guru catalogue?
The API exposes catalogue metrics and the full list of tracked APIs and providers, so you can see the current size and coverage of the directory whenever you query it.
How does an agent find APIs.guru operations in Jentic?
The agent searches Jentic by intent, such as fetching a provider's OpenAPI definition, and Jentic returns the matching operations ready to run.
GET STARTED