Google Chrome Policy API
Browse all Google APIs40
AI ReadinessFoundational (D-)40/100
Official vendor OpenAPI document · agent-readySecurityComplianceoauth214 EndpointsREST
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.
The Chrome Policy API lets Workspace administrators read, modify, and orchestrate Chrome and ChromeOS policies across organisational units, groups, and printers programmatically. It supports batch policy modification, group priority ordering for conflicting policies, network and certificate definitions for managed Wi-Fi, and resolution queries that return the effective policy for a given org unit. It is the write counterpart to the Chrome Management API.
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.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fgoogleapis.com%2Fchromepolicy" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fgoogleapis.com%2Fchromepolicy" | sh
jentic register # connects your agent to your Jentic One instanceJentic 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
Define managed Wi-Fi networks and pin certificates that ChromeOS devices must trust
Inherit or revert policies from parent org units in bulk
Upload custom policy schema files for organisations using extension-defined policies
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
POST
/v1/{+customer}/policies/networks:defineNetwork
Define a managed Wi-Fi network
Jentic AI Readiness Score
This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.
C
Chrome Policy API
- Foundational (D-)40/100
56
Foundational Compliance56
Developer Experience & Jentic Compatibility18
AI-Readiness & Agent Experience94
Agent Usability63
Security63
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
56
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: CSignals: 4
74%
Lint Results
Aggregated quality score from linter diagnostics, weighted by severity.
100%
Resolution Completeness
Percentage of `$ref` references that resolve successfully.
0%
Specification Validity
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
50%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
56
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: CSignals: 4
0%
Example Density
How richly the API is illustrated with examples.
100%
Example Validity
Percentage of examples that conform to their schemas.
25%
Response Coverage
Percentage of operations with complete response definitions (success, client error, server error).
100%
Tooling Readiness
Health of API ingestion, bundling, and resolution within Jentic pipelines.
18
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: FSignals: 4
73%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
0%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
0%
Summary Coverage
Coverage of summaries across operations/tags/info.
94
Agent Usability
Functional utility, complexity comfort, and AI orchestration readiness.
Grade: A+Signals: 1
94%
Complexity Comfort
Agent comfort level based on API operational and structural complexity.
63
Security
Trust, risk posture, and security compliance.
Grade: B-Signals: 1
62%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
63
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: BSignals: 1
63%
Descriptive Richness
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Chrome Policy API by hand means standing up Workspace OAuth with chrome.management.policy scopes, refreshing scoped access tokens, and assembling the batchModify and resolve payloads yourself. Through Jentic you install once, import the Chrome Policy API from the API Directory, store the OAuth credentials once, and your agent calls it.
Permission scoping
The API puts the customer in the URL path (/v1/{+customer}/policies:resolve, /v1/{+customer}/policies/orgunits:batchModify), so a rule can pin your agent to one customer's Chrome policies. Limit it to the operations it needs, such as resolving policies, and modifying ones like orgunit batchModify are not included unless you add them.
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.
Related APIs
Alternatives and complements available in the Jentic catalogue.
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.
GET STARTED