Google Artifact Registry API
Browse all Google APIs40
AI ReadinessFoundational (D-)40/100
Official vendor OpenAPI document · agent-readyDeveloper ToolsPackage Registryoauth234 EndpointsREST
For Agents
Manage Google Cloud Artifact Registry repositories, packages, and versions across Docker, Maven, npm, Python, apt, and yum formats.
Use for: I need to create a Docker repository in Artifact Registry in europe-west1, List every container image in a given Artifact Registry repository, Download a specific Maven artifact version from Artifact Registry, Import an existing apt repository into Artifact Registry
Not supported: Does not build artifacts, run CI pipelines, or scan images for vulnerabilities - use for storing, listing, downloading, and deleting versioned packages and container images only.
The Artifact Registry API is Google Cloud's managed service for storing and serving build artifacts including Docker container images, Maven, npm, Python, apt, and yum packages. It exposes operations to manage repositories, list and download package versions, attach files, and import artifacts from supported source formats. Repositories are scoped to a project and location, and access is governed by Cloud IAM roles bound to the registry resource. The API is the single integration surface for CI pipelines, Cloud Build, and Cloud Run when promoting and consuming versioned artifacts.
Install Jentic One Beta
Connect the Artifact Registry API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Artifact 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%2Fartifactregistry" | 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%2Fartifactregistry" | 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 Artifact Registry API.
Create, list, and delete repositories scoped to a project and region across 7+ package formats
Import apt artifacts in bulk via /v1/{+parent}/aptArtifacts:import for repository migrations
Download a package or version via /v1/{+name}:download to fetch the artifact bytes
Attach metadata files to a version with the attachments resource for SBOMs and signatures
List repository locations available to a project before deciding where to create a registry
Patch a repository to update labels, cleanup policies, or virtual repository upstreams
Use Cases
Patterns agents use Artifact Registry API for, with concrete tasks.
★ Container Image Distribution for Cloud Run and GKE
Host Docker images for Cloud Run services and GKE workloads inside a regional Artifact Registry repository, with IAM controls scoped per repository. The API exposes endpoints to create the repository, list images and tags, and delete unused versions to keep storage bounded. Pairs naturally with Cloud Build for push and Cloud Run for pull.
Create a Docker repository in europe-west1, then list all images and delete tags older than 30 days using DELETE /v1/{name}.
Language Package Hosting for Internal Libraries
Run a private Maven, npm, or Python package registry for internal libraries without operating registry infrastructure. The API allows creation of format-specific repositories, version listing, and direct artifact download for builds. Integrates with standard language tooling once the repository URL and IAM-scoped credential are configured.
Create a Python repository, list package versions matching a name prefix, and download a specific .whl via /v1/{name}:download.
Migrating apt Repositories into Google Cloud
Move an existing apt repository hosted on a self-managed server into a Google-managed Artifact Registry by calling the apt import endpoint. Imports run as long-running operations and bring all .deb packages and metadata under a single managed repository with IAM-based access control.
POST a list of source GCS URIs to /v1/{parent}/aptArtifacts:import and poll the returned operation until it completes.
AI Agent Artifact Promotion in CI
Use an AI agent to promote a build artifact from a staging repository to production by inspecting tags, copying the version, and applying a release tag. Through Jentic the agent discovers Artifact Registry operations by intent and calls them with project-scoped credentials supplied at execute time, with no Google Cloud SDK setup required in the agent runtime.
Use Jentic search for 'tag a container image in Artifact Registry', load the operation, and execute it with the source and destination repository names.
Key Endpoints
34 endpoints — the artifact registry api is google cloud's managed service for storing and serving build artifacts including docker container images, maven, npm, python, apt, and yum packages.
METHOD
PATH
DESCRIPTION
GET
/v1/{+name}/locations
List Artifact Registry locations for a project
GET
/v1/{+name}
Get a repository, package, version, tag, or attachment by resource name
DELETE
/v1/{+name}
Delete a repository, version, or tag
PATCH
/v1/{+name}
Update a repository or tag
GET
/v1/{+name}:download
Download an artifact's bytes
POST
/v1/{+parent}/aptArtifacts:import
Bulk import apt packages into a repository
POST
/v1/{+parent}/aptArtifacts:create
Create an apt artifact in a repository
GET
/v1/{+name}/locations
List Artifact Registry locations for a project
GET
/v1/{+name}
Get a repository, package, version, tag, or attachment by resource name
DELETE
/v1/{+name}
Delete a repository, version, or tag
PATCH
/v1/{+name}
Update a repository or tag
GET
/v1/{+name}:download
Download an artifact's bytes
POST
/v1/{+parent}/aptArtifacts:import
Bulk import apt packages into a repository
POST
/v1/{+parent}/aptArtifacts:create
Create an apt artifact in a repository
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
Artifact Registry API
- Foundational (D-)40/100
53
Foundational Compliance56
Developer Experience & Jentic Compatibility19
AI-Readiness & Agent Experience94
Agent Usability63
Security57
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
53
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: CSignals: 4
62%
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).
50%
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.
19
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: FSignals: 4
75%
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).
57
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: CSignals: 1
57%
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 Artifact Registry API by hand means setting up Google OAuth2, scoping a service account for registry access, and minting short-lived access tokens across its 34 operations yourself. Through Jentic you install once, import the Artifact 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}, /v1/{parent}/aptArtifacts:create), so a rule can pin your agent to one repository: it can read metadata, download artifacts, and import packages there and nothing else. You choose the operations it may call, so actions like deleting an artifact are not included unless you add them.
Credential isolation
Your Google Cloud 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 'list container images in Artifact Registry' or 'download a package version', and Jentic returns the matching operation with its input schema so the agent calls the right endpoint without traversing Google's discovery document.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Artifact Registry API through Jentic.
What authentication does the Artifact Registry API use?
The API uses Google OAuth 2.0 with cloud-platform-scoped access tokens. Service accounts authenticate via signed JWTs exchanged for access tokens and must hold the appropriate roles/artifactregistry.* IAM role on the repository. Through Jentic, the service account key sits in the encrypted vault and the agent receives only short-lived access tokens.
Which package formats does the Artifact Registry API support?
The spec exposes endpoints for Docker, Maven, npm, Python, apt, yum, and generic format repositories. The format is set when the repository is created via POST /v1/{parent}/repositories and cannot be changed afterwards.
What are the rate limits for the Artifact Registry API?
Limits are not declared in the OpenAPI spec; they are enforced as project-level quotas on artifactregistry.googleapis.com. Check the IAM and Admin > Quotas page in the Google Cloud console for your project's read and write request limits before scheduling large list or import jobs.
How do I import an apt repository through Jentic?
Run pip install jentic, then search for 'import an apt repository into Artifact Registry'. Jentic returns the POST /v1/{parent}/aptArtifacts:import operation with its schema. Execute it with a list of source GCS URIs and the target repository name; the call returns a long-running operation handle to poll.
Can I download artifact bytes through the API?
Yes. GET /v1/{name}:download returns the raw bytes for a package version. The caller must have artifactregistry.repositories.downloadArtifacts on the repository.
How do I delete unused container tags?
Send DELETE /v1/{name} where name is the full resource path of the tag or version. To automate cleanup, define a repository cleanup policy via PATCH /v1/{repository} so the registry deletes matching versions on a schedule.
Can I limit what my agent is allowed to do with the Artifact Registry API?
Yes. Because you run Jentic One yourself, your own rules decide which Artifact Registry operations and credentials the agent may use. Since this API carries the resource name in the URL path (like /v1/{name} and /v1/{parent}/aptArtifacts:create), you can pin the agent to a single repository where it only reads metadata, downloads artifacts, and imports packages. You pick the operations it may call, so a destructive action such as deleting a version or tag via DELETE /v1/{name} stays off the table unless you explicitly add it.
GET STARTED