Google API Discovery Service

Name: API Discovery Service API
Brand: API Discovery Service
Availability: InStock

✓ Official Vendor SpecDeveloper ToolsPackage Registrynone2 Endpoints

Install Jentic One Beta

Connect the API Discovery Service to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the API Discovery Service, 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.

Step 1: 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

Step 2: 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 API Discovery Service API.

List the directory of all Google APIs available through Discovery

Fetch the full Discovery REST description for any Google API and version

Extract method definitions, parameters, and request/response schemas for SDK generation

GET STARTED

Start building with API Discovery Service API

Explore with Jentic

View OpenAPI Document

For Agents

Enumerate every Google API and fetch its machine-readable description so tools, SDKs, and agents can self-bootstrap.

Use for: List all Google APIs available via the Discovery service, Get the Discovery document for a specific Google API, Find the OAuth scopes for the Google Calendar API, Retrieve the schema for the Drive v3 files resource

Not supported: Does not enable APIs, manage quotas, or proxy actual API calls - use only for reading the Google API directory and Discovery REST descriptions.

Use Cases

Patterns agents use API Discovery Service API for, with concrete tasks.

★ SDK and Client Library Generation

Tooling teams call /apis to discover every Google API, then /apis/{api}/{version}/rest to pull the Discovery document for each. The descriptions feed code generators that emit typed clients in Python, Go, Java, and TypeScript. This is exactly how the official Google API Client Libraries are produced.

Call /apis with preferred=true, then for the calendar v3 entry call /apis/calendar/v3/rest and extract every method's id, path, and parameter schema.

Scope and Permission Inventory

Security and platform teams use the Discovery API to inventory every OAuth scope declared by every Google API in a project's footprint. Pulling the full directory and extracting auth.oauth2.scopes from each Discovery doc gives a complete map of what tokens can do - useful for least-privilege reviews and risk register updates.

Call /apis with preferred=true and for each entry fetch /apis/{api}/{version}/rest, extract auth.oauth2.scopes, then return a deduplicated scope list.

Spec-Driven Integration Bootstrapping

Integration platforms (including Jentic) use Discovery as the source-of-truth for converting Google APIs into modern OpenAPI specs. Pulling /apis once on schedule produces the directory; pulling per-API REST documents produces the operational shape; conversion logic translates that into OpenAPI 3.x for tooling and agent runtimes.

Fetch /apis/drive/v3/rest, then transform the returned Discovery REST document into an OpenAPI 3 paths object preserving operationId, parameters, and request/response schemas.

Agent-Driven API Lookup

Through Jentic, an AI agent that needs to operate on a Google API it has not seen before can call the Discovery service to fetch the description on demand, then use it to build a request - all without OAuth, since Discovery is unauthenticated.

Use Jentic to search 'list Google APIs', load the schema for /apis, and execute it with preferred=true to enumerate the catalogue.

Key Endpoints

2 endpoints — google's api discovery service is the meta-api that describes every other google api.

METHOD

PATH

DESCRIPTION

GET

/apis

List the directory of Google APIs

GET

/apis/{api}/{version}/rest

Fetch the Discovery REST document for a specific API and version

GET

/apis

List the directory of Google APIs

GET

/apis/{api}/{version}/rest

Fetch the Discovery REST document for a specific API and version

Why Jentic?

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

Credential isolation

The API Discovery Service needs no credential, so there is nothing to store. Requests run through your own Jentic One instance, and no secret enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'list available Google APIs' or 'read a Discovery REST description', and Jentic returns the matching Discovery operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

Time to first call

FAQs

Specific to using API Discovery Service API through Jentic.

What authentication does the Google API Discovery Service use?

None. Both /apis and /apis/{api}/{version}/rest are public, unauthenticated GETs. Through Jentic, the call runs in the sandboxed runner without any vault credentials touching the request.

Can I get the OAuth scopes for any Google API through Discovery?

Yes. Fetch /apis/{api}/{version}/rest and read auth.oauth2.scopes - every scope the API declares is listed there with its description, which is the canonical source for least-privilege OAuth setup.

What are the rate limits for the API Discovery Service?

Google does not publish strict per-second limits for Discovery, but unreasonable polling can be throttled. Cache responses locally and re-fetch on a slow cadence (daily for the directory, weekly per-API) instead of calling on every request.

How do I list every Google API through Jentic?

Search 'list Google APIs', load the schema for /apis, then execute it. To filter to the recommended version of each API, pass preferred=true in the query parameters.

Is the Discovery REST format the same as OpenAPI?

No. Discovery is Google's own format that pre-dates OpenAPI 3. It contains similar concepts (resources, methods, parameters, schemas) but uses different field names and structures. Tools convert it to OpenAPI for compatibility with modern toolchains.

Is the Discovery Service free?

Yes. There is no charge for Discovery calls and you do not need an API key or OAuth token to read the directory or any individual Discovery REST document.

Can I limit what my agent is allowed to do with the API Discovery Service?

Yes. Because you run Jentic One yourself, your own rules decide which of the two Discovery operations the agent may call: listing the Google API directory or reading a single API's Discovery REST description. You can allow only the read that a task needs, so an agent limited to reading one REST description cannot enumerate the whole directory. The service is unauthenticated, so there are no credentials to grant, and the agent reads only the API and version you name.