Google Cloud Runtime Configuration API

Name: Cloud Runtime Configuration API
Brand: Cloud Runtime Configuration API
Availability: InStock

✓ Official Vendor SpecDeveloper ToolsMonitoring Observabilityoauth213 Endpoints

Install Jentic One Beta

Connect the Cloud Runtime Configuration API to your agent

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

Create and delete configs that group related runtime variables

Set, get, list, and delete named variables inside a config

Watch a single variable so the call returns when its value changes or a timeout elapses

GET STARTED

Start building with Cloud Runtime Configuration API

Explore with Jentic

View OpenAPI Document

For Agents

Read and write dynamic configuration variables on Google Cloud, watch them for changes, and coordinate startup with waiters that resolve when conditions are met.

Use for: Set a runtime variable named feature/checkout-flow to enabled, Watch the variable rollout/version until it changes from canary to stable, Create a waiter that blocks until 5 worker startup variables are present, List all variables under projects/my-prod/configs/orders

Not supported: Does not store secrets, manage Compute Engine metadata, or trigger workflow execution - use for sharing dynamic runtime configuration values, watchers, and waiters only.

Use Cases

Patterns agents use Cloud Runtime Configuration API for, with concrete tasks.

★ Coordinated startup of distributed services

A startup agent uses a waiter that blocks until N expected service variables are written, ensuring downstream services only begin after their dependencies have registered. The Runtime Configurator handles the timeout and success or failure semantics, so the orchestrator does not need to poll variables itself.

POST /v1beta1/{+parent}/waiters with success.cardinality.number=5 and a 10-minute timeout, then poll the waiter until done.

Feature flag rollout

A release agent stores feature flags as runtime variables. Services watch each variable through the watch endpoint and react when the agent sets the value to enabled or disabled. The watch call returns as soon as the value changes, providing near-real-time flag propagation without polling.

Have services call POST /v1beta1/{+name}:watch on feature/checkout-flow; the agent issues PUT /v1beta1/{+name} to flip the value when ready.

IAM-scoped config access for multi-team projects

A platform team partitions runtime variables by config and binds IAM principals per config so each team only reads and writes its own. setIamPolicy and getIamPolicy on each config govern those grants, and testIamPermissions lets agents check rights before attempting privileged operations.

POST /v1beta1/{+resource}:setIamPolicy on each config with the team's group bound to roles/runtimeconfig.admin.

Agent-driven runtime flags through Jentic

An AI agent built on Jentic flips runtime configuration values on behalf of operators. It searches for the variable update operation by intent, loads the schema, executes the change, and reports back. OAuth tokens stay isolated in your Jentic One instance so raw secrets never enter agent context.

Search Jentic for 'set runtime configurator variable', load the PUT variable schema, execute against projects/my-prod/configs/orders/variables/feature/checkout-flow with value=enabled.

Key Endpoints

13 endpoints — the cloud runtime configuration api exposes the runtime configurator, which lets services dynamically configure and share variables across google cloud workloads.

METHOD

PATH

DESCRIPTION

POST

/v1beta1/{+parent}/configs

Create a config

POST

/v1beta1/{+parent}/variables

Create a variable inside a config

GET

/v1beta1/{+name}

Get a config, variable, or waiter

PUT

/v1beta1/{+name}

Update a variable value

DELETE

/v1beta1/{+name}

Delete a config, variable, or waiter

POST

/v1beta1/{+name}:watch

Watch a variable for changes

POST

/v1beta1/{+parent}/waiters

Create a waiter

POST

/v1beta1/{+resource}:setIamPolicy

Set the IAM policy on a config

POST

/v1beta1/{+parent}/configs

Create a config

POST

/v1beta1/{+parent}/variables

Create a variable inside a config

GET

/v1beta1/{+name}

Get a config, variable, or waiter

PUT

/v1beta1/{+name}

Update a variable value

DELETE

/v1beta1/{+name}

Delete a config, variable, or waiter

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 'set a runtime configurator variable' or 'watch a runtime variable', and Jentic returns the matching operation with its input schema so the agent calls the right endpoint without reading the discovery document.

Time to first call

FAQs

Specific to using Cloud Runtime Configuration API through Jentic.

What authentication does the Runtime Configuration API use?

It uses Google OAuth 2.0 with the cloud-platform or cloudruntimeconfig scopes, declared as Oauth2 and Oauth2c. Through Jentic, OAuth tokens are stored encrypted in the vault and exchanged for short-lived access tokens at execution time so raw refresh tokens never reach the agent.

Can I watch a runtime variable for changes through the API?

Yes. POST /v1beta1/{+name}:watch performs a long-poll request that returns as soon as the named variable changes value or a server-side timeout elapses. This avoids client-side polling and gives near-real-time propagation of feature flags and rollout signals.

What are the rate limits for the Runtime Configuration API?

Google Cloud applies per-project read and write quotas to the Runtime Configurator, with watch and waiter calls counted against a separate concurrent-long-poll quota. The default per-minute quota is 600 read requests per project, raisable through the Cloud Console for sustained usage.

How do I create a waiter through Jentic?

Search Jentic for 'create runtime configurator waiter', load the schema for POST /v1beta1/{+parent}/waiters, and execute with the cardinality success condition and timeout you need. Jentic returns the waiter resource, which the agent polls until status reports done.

Is the Runtime Configuration API free?

The API is free to call within Google Cloud quotas, and stored variables and waiters incur no per-byte charge inside published limits. Costs scale only with very large variable bodies above the per-config size limits.

How do I scope variable access to one team only?

Place each team's variables in its own config and bind a team-specific IAM principal to the config with POST /v1beta1/{+resource}:setIamPolicy at the role roles/runtimeconfig.admin or .viewer. Other principals can be denied entirely at the config level rather than on each variable.

Can I limit what my agent is allowed to do with the Cloud Runtime Configuration API?

Yes. Because this API carries the config and variable in the URL path (/v1beta1/{+name} and /v1beta1/{+parent}/variables), your self-hosted Jentic One instance lets you write a rule that pins the agent to a single runtime config so it can only read and watch variables there. You decide which operations the agent may call, so state-changing ones like deleting a variable (DELETE /v1beta1/{+name}) or setting an IAM policy (POST /v1beta1/{+resource}:setIamPolicy) are excluded unless you explicitly add them. The Google OAuth credential stays in your own instance, and a scoped token is injected only for the operations you allow.

Google Cloud Runtime Configuration API

Connect the Cloud Runtime Configuration API to your agent

Capabilities

Start building with Cloud Runtime Configuration API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs