Google Artifact Registry API

Name: Artifact Registry API
Brand: Artifact Registry API
Availability: InStock

✓ Official Vendor SpecDeveloper ToolsPackage Registryoauth234 EndpointsREST

For Agents

Manage Google Cloud Artifact Registry repositories, packages, and versions across Docker, Maven, npm, Python, apt, and yum formats.

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.

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 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

GET STARTED

Start building with Artifact Registry API

Explore with Jentic

View OpenAPI Document

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.

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

Why Jentic?

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

Credential isolation

Google service account keys are encrypted in the Jentic vault. Agents call Artifact Registry through Jentic with short-lived access tokens minted on demand, never seeing the JSON key file in their context.

Intent-based discovery

Agents search by intent (e.g. 'list container images in Artifact Registry') and Jentic returns the matching Artifact Registry operation with its input schema, instead of the agent traversing Google's discovery document.

Time to first call

Direct integration: 1-3 days for service account setup, IAM bindings, and SDK wiring. Through Jentic: under 1 hour once the service account credential is registered in the vault.

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.

Google Artifact Registry API

Connect the Artifact Registry API to your agent

Capabilities

Start building with Artifact Registry API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs