Google Cloud Run Admin API

Name: Cloud Run Admin API
Brand: Cloud Run Admin API
Availability: InStock

✓ Official Vendor SpecCloud InfrastructureServerlessoauth225 EndpointsREST

For Agents

Deploy container images as autoscaling Cloud Run services and jobs, manage revisions, and run jobs with overrides programmatically.

Install Jentic One Beta

Connect the Cloud Run Admin API to your agent

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

Deploy a container image as an autoscaling Cloud Run service with custom CPU, memory, and concurrency

Trigger one-off Cloud Run job executions with parameter overrides for batch workloads

List, get, and delete revisions to roll back or audit deployment history

GET STARTED

Start building with Cloud Run Admin API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Cloud Run Admin API for, with concrete tasks.

★ GitOps-driven service deployment

A deployment agent watches a container registry for new tags, calls the Cloud Run service create or replace endpoint to roll forward to the new image, waits on the long-running operation, and reports success back to the GitOps controller. The Admin API v2 returns operation handles that the agent can poll or cancel deterministically.

Call the Cloud Run service create endpoint with an image reference, then call /v2/{+name}:wait until the long-running operation reports done.

Scheduled job execution

A batch agent triggers nightly Cloud Run jobs with environment-variable overrides — for example, the date partition to process — and monitors the resulting executions for completion or failure. POST /v2/{+name}:run launches the job execution and returns an operation that the agent waits on.

POST /v2/{+name}:run on the nightly-etl job with overrides setting RUN_DATE=2026-06-09, then poll the operation until done.

Safe rollback on incident

When a release agent detects elevated 5xx rates, it lists revisions for the affected service, identifies the previous healthy revision, and patches the service traffic configuration to send 100% of traffic back to it. This contains incidents in seconds without redeploying the previous image.

List revisions under the affected service, then PATCH the service to set traffic.percent=100 on the prior revision name.

Agent-driven container deploys through Jentic

An AI agent built on Jentic deploys and updates Cloud Run services on behalf of developers. It searches for the deploy operation by intent, loads the schema, executes the call, and waits on the operation. OAuth tokens stay isolated in Jentic's vault, and the agent never holds a service-account key.

Search Jentic for 'deploy container to cloud run', load the create-service schema, execute against projects/my-prod/locations/us-central1, then call wait until done.

Key Endpoints

25 endpoints — the cloud run admin api v2 deploys and manages user-supplied container images that scale automatically based on incoming requests, aligned with google cloud aip-based api standards.

METHOD

PATH

DESCRIPTION

GET

/v2/{+name}

Get a Cloud Run service, job, or revision

PATCH

/v2/{+name}

Patch a service or job

DELETE

/v2/{+name}

Delete a service, job, or revision

POST

/v2/{+name}:run

Run a Cloud Run job

POST

/v2/{+name}:wait

Wait on a long-running operation

POST

/v2/{+name}:cancel

Cancel a long-running operation

POST

/v2/{+name}:exportImage

Export an image associated with a service

GET

/v2/{+name}:exportImageMetadata

Export metadata for an image

GET

/v2/{+name}

Get a Cloud Run service, job, or revision

PATCH

/v2/{+name}

Patch a service or job

DELETE

/v2/{+name}

Delete a service, job, or revision

POST

/v2/{+name}:run

Run a Cloud Run job

POST

/v2/{+name}:wait

Wait on a long-running operation

Why Jentic?

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

Credential isolation

Cloud Run OAuth 2.0 credentials and service-account keys are stored encrypted in the Jentic vault. Agents receive scoped, short-lived access tokens minted at call time; raw key material never enters the agent context.

Intent-based discovery

Agents search Jentic with intents like 'deploy container to cloud run' or 'run cloud run job', and Jentic returns the matching v2 admin operation with its full request schema, so the agent calls the correct endpoint without reading the discovery document.

Time to first call

Direct integration takes 2-4 days for OAuth wiring, long-running operation polling, and traffic shifting logic. Through Jentic the same deploy flow is under 1 hour: search, load, execute, wait.

FAQs

Specific to using Cloud Run Admin API through Jentic.

What authentication does the Cloud Run Admin API use?

It uses Google OAuth 2.0 with the cloud-platform scope, declared as Oauth2 and Oauth2c. Service-account credentials and refresh tokens are typically used; through Jentic these stay encrypted in the vault, with the agent receiving a short-lived access token at execution time.

Can I run Cloud Run jobs with overrides through the Admin API?

Yes. POST /v2/{+name}:run executes a Cloud Run job and accepts overrides for environment variables, args, and timeouts on a per-execution basis. The endpoint returns a long-running operation that the agent can poll with /v2/{+name}:wait or cancel with /v2/{+name}:cancel.

What are the rate limits for the Cloud Run Admin API?

Google Cloud applies per-project quotas to Cloud Run admin calls; the default is 600 mutate requests per minute per project for service and job updates. Long-running operations also count against the maximum concurrent operations quota, which can be raised through the Cloud Console.

How do I deploy a container to Cloud Run through Jentic?

Search Jentic for 'deploy container to cloud run', load the schema for the service create endpoint, and execute with parent set to projects/PROJECT/locations/LOCATION and the desired image and resource limits. Jentic returns the operation handle so the agent can wait on completion before sending traffic.

Is the Cloud Run Admin API free?

The API itself is free to call within Google Cloud quotas; you pay only for the Cloud Run service or job execution time, billed per CPU-second and memory-GB-second with a generous free tier. Idle services with minScale=0 incur no charge between requests.

How do I roll back to a previous Cloud Run revision?

List revisions for the service with GET /v2/{+name}/revisions, then PATCH the service to set its traffic split to 100% on the previous revision name. The service immediately stops sending traffic to the broken revision without redeploying or rebuilding the image.

Google Cloud Run Admin API

Connect the Cloud Run Admin API to your agent

Capabilities

Start building with Cloud Run Admin API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs