Google Remote Build Execution API

Name: Remote Build Execution API
Brand: Remote Build Execution API
Availability: InStock

✓ Official Vendor SpecDeveloper ToolsCi Cdoauth213 Endpoints

Install Jentic One Beta

Connect the Remote Build Execution API to your agent

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

Create, list, get, update, and delete RBE instances scoped to a Google Cloud project

Manage worker pools that determine the machine type and concurrency available to a build farm

Provision specialized AndroidCI, Kokoro, and Guitar instances from a single endpoint

GET STARTED

Start building with Remote Build Execution API

Explore with Jentic

View OpenAPI Document

For Agents

Provision and manage Bazel-compatible Remote Build Execution instances and worker pools, and configure IAM bindings that control which jobs can submit builds.

Use for: Provision a new Remote Build Execution instance for the Bazel build cluster, Add a worker pool of n2-standard-32 machines to my RBE instance, List all worker pools attached to projects/my-org/instances/build-farm, Delete the legacy AndroidCI instance that is no longer in use

Not supported: Does not execute Bazel actions, store build cache contents, or schedule individual remote actions - use for administrative lifecycle of RBE instances, worker pools, and IAM bindings only.

Use Cases

Patterns agents use Remote Build Execution API for, with concrete tasks.

★ Auto-scaling Bazel build farm

A build platform team auto-scales worker pools attached to their RBE instance based on weekday traffic, calling the worker pool update endpoint to expand capacity in the morning and shrink it overnight. Coupled with the Remote Execution API on the data plane, this keeps Bazel build queue times bounded while controlling spend.

Call PATCH /v1alpha/{+name} on each worker pool under projects/my-org/instances/build-farm to set workerCount=200 at 09:00 and 30 at 21:00.

Disposable per-team RBE instances

Each platform team gets a dedicated RBE instance provisioned from a template. An agent calls instance create to spin up the instance, attaches a sized worker pool, and binds the team's service account through createBackendIAMBinding. When the team is offboarded, the agent reverses the calls.

POST /v1alpha/{+parent}/instances to create instance team-x, POST /v1alpha/{+parent}/workerpools to attach a 100-worker pool, and POST /v1alpha/{+parent}:createBackendIAMBinding for the team service account.

Notification health checks

Operators rely on RBE notifications for build farm degradation alerts. An agent runs a daily synthetic test by calling testNotify on each instance, confirming that the configured channel still delivers, and opening an incident when delivery fails. This catches misconfigured channels before a real outage.

Iterate RBE instances under projects/my-org and call POST /v1alpha/{+name}:testNotify on each, recording the response status.

Agent-managed build farms through Jentic

An AI agent provisions short-lived RBE instances for migration testing through Jentic. It searches for the create operation by intent, runs the call, attaches a worker pool, and decommissions the instance once the migration verification job completes. OAuth tokens stay isolated in your Jentic One instance.

Search Jentic for 'create remote build execution instance', execute the create against projects/migration, attach a worker pool, then call delete after the job exits.

Key Endpoints

13 endpoints — the google remote build execution api administers rbe instances and worker pools used to scale bazel and other remote execution-api-compatible builds across distributed worker fleets.

METHOD

PATH

DESCRIPTION

POST

/v1alpha/{+parent}/instances

Create an RBE instance

GET

/v1alpha/{+name}

Get an RBE instance or worker pool

PATCH

/v1alpha/{+name}

Update an RBE instance or worker pool

DELETE

/v1alpha/{+name}

Delete an RBE instance or worker pool

POST

/v1alpha/{+parent}/workerpools

Create a worker pool attached to an instance

POST

/v1alpha/{+parent}:createBackendIAMBinding

Bind an IAM principal to an RBE backend

POST

/v1alpha/{+parent}:deleteBackendIAMBinding

Remove an IAM binding from an RBE backend

POST

/v1alpha/{+name}:testNotify

Send a test notification for an instance

POST

/v1alpha/{+parent}/instances

Create an RBE instance

GET

/v1alpha/{+name}

Get an RBE instance or worker pool

PATCH

/v1alpha/{+name}

Update an RBE instance or worker pool

DELETE

/v1alpha/{+name}

Delete an RBE instance or worker pool

POST

/v1alpha/{+parent}/workerpools

Create a worker pool attached to an instance

Why Jentic?

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

Credential isolation

Your Google OAuth credential is stored once, encrypted, by your own Jentic One instance and a scoped access token is injected at execution time. The credential never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'create a Remote Build Execution instance' or 'add a worker pool', and Jentic returns the matching admin operation with its input schema so the agent calls the right endpoint without browsing the discovery document.

Time to first call

FAQs

Specific to using Remote Build Execution API through Jentic.

What authentication does the Remote Build Execution API use?

It uses Google OAuth 2.0 with the cloud-platform scope, declared as Oauth2 and Oauth2c. Through Jentic, refresh tokens and service-account credentials are held encrypted in your Jentic One instance and exchanged for short-lived access tokens at execution time.

Can I create worker pools through the Remote Build Execution API?

Yes. POST /v1alpha/{+parent}/workerpools creates a worker pool attached to an existing RBE instance, accepting machine type, worker count, disk size, and accelerator configuration. The endpoint returns a long-running operation that the agent polls until the workers are ready.

What are the rate limits for the Remote Build Execution API?

Google Cloud applies per-project quotas to RBE control-plane calls; the dominant constraints are the maximum number of instances and worker pools per project, both raisable through the Cloud Console quotas page. Read calls have a per-minute quota that scales with project usage.

How do I provision an RBE instance through Jentic?

Search Jentic for 'create remote build execution instance', load the schema for POST /v1alpha/{+parent}/instances, and execute with parent set to projects/PROJECT and the desired instance ID. Jentic exposes the long-running operation so the agent can poll until done before attaching worker pools.

Is the Remote Build Execution API free?

The control-plane API itself is free within Google Cloud quotas, but the worker machines and any Cloud Storage used for the build cache are billed at standard Compute Engine and Cloud Storage rates. Costs scale with worker count, machine type, and uptime.

How do I send a test notification through the RBE API?

Call POST /v1alpha/{+name}:testNotify with the instance resource name. The endpoint pushes a synthetic event through the configured notification channel, and the response indicates whether the channel accepted the message - useful for detecting silently broken alerting before an incident occurs.

Can I limit what my agent is allowed to do with the Remote Build Execution API?

Yes. Because this API carries the instance and worker pool in the URL path (/v1alpha/{+name} and /v1alpha/{+parent}/workerpools), your self-hosted Jentic One instance lets you write a rule that pins the agent to a single RBE instance, where it can read and create worker pools and nothing else. You decide which operations the agent may call, so state-changing calls like deleting an instance or removing a backend IAM binding stay out of reach unless you explicitly add them. Your own rules govern which operations and OAuth credentials the agent uses, and those credentials are held by your Jentic One instance rather than exposed to the agent.

Google Remote Build Execution API

Connect the Remote Build Execution API to your agent

Capabilities

Start building with Remote Build Execution API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs