Google Apigee Registry API
Browse all Google APIs39
AI ReadinessNon-Ready (F)39/100
Official vendor OpenAPI document · agent-readyDeveloper ToolsPackage Registryoauth226 EndpointsREST
For Agents
Catalog, version, and govern OpenAPI and other machine-readable specs in a Google Cloud-managed registry. Useful for agents that maintain an enterprise API inventory or governance pipeline.
Use for: Register a new API in the registry, Upload a new OpenAPI spec revision under an existing API version, Roll back a spec to the previous revision, Attach a lint report artifact to a spec
Not supported: Does not handle runtime traffic, proxy execution, or developer portal hosting - use for cataloging, versioning, and governing API specs and deployments only.
The Apigee Registry API stores, versions, and indexes API descriptions and machine-readable specs in a Google Cloud project. It models APIs, ApiVersions, ApiSpecs, ApiDeployments, and Artifacts as first-class resources, exposes revisions and rollback for specs, and supports artifact storage for governance metadata such as scorecards and lint reports. It works alongside Apigee runtime but does not depend on it.
Install Jentic One Beta
Connect the Apigee Registry API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Apigee Registry API, 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%2Fgoogleapis.com%2Fapigeeregistry" | 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%2Fgoogleapis.com%2Fapigeeregistry" | 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 Apigee Registry API.
Register APIs, versions, specs, and deployments as governed resources
Manage spec revisions and roll back to a previous known-good version
Attach artifacts (scorecards, lint reports, owners) to any registry resource
Retrieve raw spec contents for downstream tooling
List and search APIs across a Google Cloud organization
Track long-running operations for registry mutations
Use Cases
Patterns agents use Apigee Registry API for, with concrete tasks.
★ Enterprise API inventory and governance
Platform teams use the registry as the source of truth for every API the company exposes, internal or external. APIs, versions, specs, and deployments are first-class resources with revisions, so governance teams can answer 'what is the contract for v3?' or 'who owns this API?' from a stable, queryable surface.
Register API 'orders', create version 'v1', upload openapi.yaml as a spec revision, and tag it with artifact 'owner=payments-team'.
Spec revision and rollback
Specs evolve. The registry's revisions and rollback endpoints let teams keep a clean linear history, mark known-good revisions, and revert to a previous revision without losing the breaking-change attempt for diffing later.
Roll back the current spec under projects/p/locations/global/apis/orders/versions/v1/specs/openapi to its previous revision and confirm via the returned resource.
Artifact-driven governance
Lint scores, security scans, and ownership metadata attach as artifacts to APIs, versions, or specs. CI pipelines write artifacts on every spec push so dashboards and gating policies can read a single, structured place rather than scraping spreadsheets.
Attach an artifact named 'lint-report' with mimeType application/json containing the latest spectral output to spec 'openapi' under version v1 of API orders.
AI agent governance assistant via Jentic
An AI agent reviews PRs that update OpenAPI specs, runs lint and breaking-change checks, and writes the results back to the registry as artifacts through Jentic. The agent calls the registry without holding the project's service account credentials directly.
After a PR merges, upload the new spec revision, attach a generated lint-report artifact, and post a summary into the PR thread.
Key Endpoints
26 endpoints — the apigee registry api stores, versions, and indexes api descriptions and machine-readable specs in a google cloud project.
METHOD
PATH
DESCRIPTION
GET
/v1/{+name}/locations
List available locations
GET
/v1/{+name}/operations
List long-running operations
POST
/v1/{+name}:cancel
Cancel a long-running operation
DELETE
/v1/{+name}:deleteRevision
Delete a specific revision
GET
/v1/{+name}:getContents
Get raw spec contents
GET
/v1/{+name}:listRevisions
List revisions of a spec
POST
/v1/{+name}:rollback
Roll back a spec to a previous revision
GET
/v1/{+name}/locations
List available locations
GET
/v1/{+name}/operations
List long-running operations
POST
/v1/{+name}:cancel
Cancel a long-running operation
DELETE
/v1/{+name}:deleteRevision
Delete a specific revision
GET
/v1/{+name}:getContents
Get raw spec contents
GET
/v1/{+name}:listRevisions
List revisions of a spec
POST
/v1/{+name}:rollback
Roll back a spec to a previous revision
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
Apigee Registry API
- Non-Ready (F)39/100
68
Foundational Compliance56
Developer Experience & Jentic Compatibility17
AI-Readiness & Agent Experience94
Agent Usability63
Security49
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
68
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: B+Signals: 4
71%
Lint Results
Aggregated quality score from linter diagnostics, weighted by severity.
100%
Resolution Completeness
Percentage of `$ref` references that resolve successfully.
0%
Specification Validity
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
100%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
56
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: CSignals: 4
0%
Example Density
How richly the API is illustrated with examples.
100%
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.
17
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: FSignals: 4
69%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
0%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
0%
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.
63
Security
Trust, risk posture, and security compliance.
Grade: B-Signals: 1
62%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
49
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: D+Signals: 1
49%
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
Wiring the Apigee Registry API by hand means configuring Google OAuth2, scoping a service account for registry access, and minting access tokens for each spec and revision call yourself. Through Jentic you install once, import the Apigee Registry API from the API Directory, store the OAuth credential once, and your agent calls it.
Permission scoping
This API puts the resource name in the URL path (/v1/{name}:getContents, /v1/{name}:listRevisions), so a rule can pin your agent to one registry resource: it can read contents and list revisions there and nothing else. You choose the operations it may call, so actions like deleting a revision or rolling back are not included unless you add them.
Credential isolation
Your Apigee Registry OAuth credential is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'register an API spec' or 'roll back an API version', and Jentic returns the matching registry operation with its input schema so the agent calls the right endpoint without reading the registry reference.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Apigee Registry API through Jentic.
What authentication does the Apigee Registry API use?
OAuth 2.0 with Google Cloud credentials. Through Jentic the service account JSON is vaulted and exchanged for scoped access tokens at runtime.
Can I roll back a spec to a previous revision?
Yes. Specs are revisioned, and the rollback endpoint at /v1/{+name}:rollback restores a prior revision while preserving the failed revision for diffing. Use listRevisions to enumerate available revisions before rolling back.
What are the rate limits for the Apigee Registry API?
Standard Google Cloud per-project per-minute quotas apply. The registry is a control-plane service and is rarely the bottleneck; large-scale spec uploads should still batch through API operations rather than parallelising thousands of concurrent calls.
How do I store an OpenAPI spec through Jentic?
Search Jentic for 'upload API spec to apigee registry', load the schema for the apis.versions.specs.create operation, and execute it with the API name, version name, and base64-encoded spec contents. Jentic returns the new spec revision name.
Is the Apigee Registry API free?
Apigee Registry is part of the Apigee product family. Pricing is documented under Apigee; the registry is generally available without a separate per-call fee, but storage and operations roll up under your Apigee billing.
Do I need Apigee runtime to use the registry?
No. The registry can be used independently to track specs and deployments even if your runtime is API Gateway, AWS, or anything else. ApiDeployment records simply describe where a version is hosted.
Can I limit what my agent is allowed to do with the Apigee Registry API?
Yes. Because you run Jentic One yourself, your own rules decide which registry operations and which OAuth credential your agent may use. The Apigee Registry API puts the resource name in the URL path (for example /v1/{name}:getContents and /v1/{name}:listRevisions), so you can pin an agent to a single registry resource and let it only read contents and list revisions there. Destructive actions like :rollback or :deleteRevision stay off unless you explicitly grant them.
GET STARTED