Google Apigee Registry API
Browse all Google APIs✓ Official Vendor SpecDeveloper 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://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh2
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 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
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
Google Cloud service account credentials for the Apigee Registry are stored encrypted in the Jentic vault. Agents call registry operations through Jentic with scoped access tokens; the JSON key never enters the agent context.
Intent-based discovery
Agents search Jentic with phrases like 'register api spec' or 'rollback api version' and Jentic returns the matching registry operation with its input schema, so the agent does not need to read the registry reference.
Time to first call
Direct integration: 1-3 days for IAM, gcloud setup, and revisioning logic. Through Jentic: under one hour to start indexing, revising, and tagging specs.
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.
GET STARTED