Google Chrome Policy API

Name: Chrome Policy API
Brand: Google Chrome Policy API
Availability: InStock

✓ Official Vendor SpecSecurityComplianceoauth214 EndpointsREST

Install Jentic One Beta

Connect the Chrome Policy API to your agent

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

Resolve the effective Chrome policy for a given org unit, group, or printer

Batch-modify policies on multiple org units in a single call to reduce drift windows

Apply group-targeted policies and reorder them when multiple groups affect the same user

GET STARTED

Start building with Chrome Policy API

Explore with Jentic

View OpenAPI Document

For Agents

Apply, modify, and resolve Chrome and ChromeOS policies across org units, groups, and printers in a Google Workspace customer.

Use for: Resolve the effective Chrome policy for an org unit, Apply a Chrome policy to multiple org units at once, Update group priority ordering for conflicting Chrome policies, Define a managed Wi-Fi network for ChromeOS devices

Not supported: Does not read fleet telemetry, manage Workspace users, or push files to devices - use for Chrome and ChromeOS policy resolution and modification only.

Use Cases

Patterns agents use Chrome Policy API for, with concrete tasks.

★ Bulk Policy Rollout

Workspace admins push a policy change - for example, disabling a specific extension or enforcing a new homepage - across many org units at once via batchModify. The single batched call avoids drift windows where some org units have the new policy and others still hold the old value. The API also supports batchInherit to revert a unit to its parent's policy.

POST /v1/{customer}/policies/orgunits:batchModify with a policy disabling the chrome.urlBlocklist override across three org units.

Managed Wi-Fi Provisioning

IT teams define corporate Wi-Fi networks and trust certificates centrally and the API rolls them out to ChromeOS devices in scope. defineNetwork and defineCertificate handle creation, removeNetwork and removeCertificate handle removal. This eliminates manual provisioning on each device.

POST /v1/{customer}/policies/networks:defineNetwork with a WPA2-Enterprise profile for the corporate SSID and target the engineering org unit.

Group Priority Conflict Resolution

When users belong to multiple Workspace groups whose Chrome policies conflict, admins use updateGroupPriorityOrdering to set the precedence order. listGroupPriorityOrdering returns the current order so changes can be reviewed before commit. This is the recommended way to handle policy fan-out in large organisations.

POST /v1/{customer}/policies/groups:updateGroupPriorityOrdering with the desired ordered list of group ids for the chrome.users.bookmarkBarEnabled policy.

AI Agent Workspace Policy Operator via Jentic

An AI agent through Jentic acts as a junior IT operator - resolving the effective policy for an org unit, applying a policy change after admin confirmation, and verifying the new effective policy. Jentic isolates the Workspace OAuth credentials so the agent never holds the admin refresh token directly.

Through Jentic, search chromepolicy_resolve, load schema, and execute it for org unit /Engineering returning all schemas under chrome.users.*.

Key Endpoints

14 endpoints — the chrome policy api lets workspace administrators read, modify, and orchestrate chrome and chromeos policies across organisational units, groups, and printers programmatically.

METHOD

PATH

DESCRIPTION

POST

/v1/{+customer}/policies:resolve

Resolve the effective policy for a target

POST

/v1/{+customer}/policies/orgunits:batchModify

Modify policies on multiple org units

POST

/v1/{+customer}/policies/orgunits:batchInherit

Inherit policies from parent on multiple org units

POST

/v1/{+customer}/policies/groups:batchModify

Modify policies for multiple groups

POST

/v1/{+customer}/policies/groups:updateGroupPriorityOrdering

Set group priority ordering for a policy

POST

/v1/{+customer}/policies/networks:defineNetwork

Define a managed Wi-Fi network

POST

/v1/{+customer}/policies:resolve

Resolve the effective policy for a target

POST

/v1/{+customer}/policies/orgunits:batchModify

Modify policies on multiple org units

POST

/v1/{+customer}/policies/orgunits:batchInherit

Inherit policies from parent on multiple org units

POST

/v1/{+customer}/policies/groups:batchModify

Modify policies for multiple groups

POST

/v1/{+customer}/policies/groups:updateGroupPriorityOrdering

Set group priority ordering for a policy

Why Jentic?

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

Credential isolation

Your Workspace OAuth credentials with chrome.management.policy scopes are stored once, encrypted, by your own Jentic One instance and injected at execution time. The agent receives only short-lived access tokens and the refresh token never enters its prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'apply a Chrome policy to an org unit', and Jentic returns the orgunits batchModify operation with its parameter schema so the agent calls the right endpoint without browsing the reference docs.

Time to first call

FAQs

Specific to using Chrome Policy API through Jentic.

What authentication does the Chrome Policy API use?

It requires OAuth 2.0 with the chrome.management.policy or chrome.management.policy.readonly scope on a Workspace super admin or delegated admin. Through Jentic, the credential is stored encrypted in your Jentic One instance and the agent receives only short-lived scoped access tokens.

Can I apply a policy to multiple org units at once?

Yes. POST /v1/{customer}/policies/orgunits:batchModify with a list of policy modifications, each targeting a different org unit. The API processes the batch atomically per request and returns per-modification status.

What are the rate limits for the Chrome Policy API?

Google enforces a per-project per-minute quota of around 240 write requests and higher read quotas. Use the batch endpoints (batchModify, batchInherit) to make bulk changes within quota rather than one-policy-at-a-time updates.

How do I resolve the effective policy for an org unit through Jentic?

Use the Jentic search query "resolve Chrome policy for an org unit" to discover the customers.policies.resolve operation, load its schema, and execute it with the customer id, policySchemaFilter, and the target org unit. Run pip install jentic to get started.

Can the Chrome Policy API target individual users?

It targets org units, groups, and printers - not individual users directly. To apply a policy to a single user, place the user in an org unit or group whose policy is configured accordingly.

Is the Chrome Policy API free?

It is included with Chrome Enterprise Upgrade and ChromeOS Enterprise licences. There is no per-call charge from Google for policy resolution and modification.

Can I limit what my agent is allowed to do with the Google Chrome Policy API?

Yes. Because you self-host Jentic One, your own rules decide which Chrome Policy operations and credentials the agent may use, and the customer id sits in the URL path (/v1/{customer}/policies:resolve, /v1/{customer}/policies/orgunits:batchModify), so a rule can pin the agent to a single Workspace customer. You can allow only read-style operations such as resolving the effective policy for an org unit while withholding write operations like orgunits:batchModify, groups:batchModify, or networks:defineNetwork unless you explicitly grant them. Your Workspace OAuth credentials stay encrypted in your instance and the agent receives only short-lived scoped access tokens.

Google Chrome Policy API

Connect the Chrome Policy API to your agent

Capabilities

Start building with Chrome Policy API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs