Remote Build Execution API

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

✓ Official Vendor SpecDeveloper ToolsCi Cdoauth213 EndpointsREST

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.

Quickstart

Get started with Remote Build Execution API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"create remote build execution instance"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Remote Build Execution API 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

Bind and unbind IAM principals on RBE backends so build clients can authenticate

GET STARTED

Start building with Remote Build Execution API API

Explore with Jentic

View OpenAPI Document

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.

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. It supports creating, listing, updating, and deleting RBE instances, configuring worker pools that supply the build farm, and managing IAM bindings that govern who can submit work. Specialized create endpoints exist for AndroidCI, Kokoro, and Guitar instances, alongside a notification-test endpoint for verifying alert delivery.

Use Cases

Patterns agents use Remote Build Execution API 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 the Jentic vault.

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 though Jentic?

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

Credential isolation

Google OAuth 2.0 client secrets and service-account keys for the RBE Admin API are stored encrypted in the Jentic vault. Agents call RBE through scoped access tokens minted at execution time so raw credentials never enter agent context.

Intent-based discovery

Agents search Jentic with intents like 'create remote build execution instance' or 'add worker pool to rbe', and Jentic returns the matching admin operation with its full schema, so the agent calls the correct endpoint without browsing the discovery document.

Time to first call

Direct integration with the RBE Admin API takes 3-5 days to wire OAuth, long-running operation polling, and worker pool sizing logic. Through Jentic the same provisioning flow is under 1 hour: search, load, execute, poll.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Cloud Build API

Managed CI service that runs builds without operating an RBE worker pool.

Choose Cloud Build for general-purpose CI; choose Remote Build Execution when the workload is Bazel-native and benefits from a remote action cache.

Complementary

Compute Engine API

Supplies the underlying VM types that worker pools provision.

Use Compute to inspect VM availability and quotas; use RBE to attach those machines as build workers.

Complementary

Artifact Registry API

Stores the container images and packages produced by RBE-driven builds.

Use Artifact Registry to host build outputs; use RBE to produce them at scale.

Complementary

Cloud IAM API

Manages the IAM principals that RBE backend bindings reference.

Use IAM to create the service account; use RBE backend IAM bindings to grant it submit rights on a specific backend.

FAQs

Specific to using Remote Build Execution API 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 the Jentic vault 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.