Google Cloud Resource Manager API
Browse all Google APIs41
AI ReadinessFoundational (D-)41/100
Official vendor OpenAPI document · agent-readyCloud InfrastructureComputeoauth228 EndpointsREST
For Agents
Programmatically create, list, and update GCP projects, folders, organizations, and tags, plus manage IAM bindings on those resource containers. Lets agents structure tenancy and apply policy across a Google Cloud hierarchy.
Use for: I need to create a new Google Cloud project under a folder, List all folders my service account can access, Search for projects whose display name contains a keyword, Get the IAM policy attached to a specific organization
Not supported: Does not provision compute, storage, or networking resources, and does not manage service account keys - use for the GCP project, folder, organization, and tag hierarchy only.
The Cloud Resource Manager API creates, reads, and updates metadata for Google Cloud Platform resource containers including projects, folders, organizations, tag keys, and tag values. It exposes hierarchical IAM controls for managing access to those containers and supports lien protection to prevent accidental project deletion. Resource Manager is the foundation for organizing GCP resources at scale and underpins billing, policy enforcement, and asset inventory across the platform.
Install Jentic One Beta
Connect the Cloud Resource Manager API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Cloud Resource Manager 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%2Fcloudresourcemanager" | 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%2Fcloudresourcemanager" | 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 Cloud Resource Manager API.
Create and undelete GCP projects under a parent folder or organization
Search and list folders, organizations, and projects accessible to the caller
Get, set, and test IAM policies on projects, folders, and organizations
Apply tag keys and tag values to resources for policy and billing segmentation
Place liens on projects to prevent unintended deletion
Look up effective tags inherited through the resource hierarchy
Use Cases
Patterns agents use Cloud Resource Manager API for, with concrete tasks.
★ Programmatic Project Provisioning
Automate the creation of new Google Cloud projects for each customer, environment, or workload. Cloud Resource Manager exposes project create, get, and update operations alongside folder placement so platform teams can spin up isolated tenants on demand and attach the correct billing account and tags. End-to-end provisioning typically completes in under a minute per project.
Create a new project named acme-prod-eu under folder folders/12345 and tag it with environment=production
Hierarchy-Wide IAM Audit
Enumerate organizations, folders, and projects to retrieve their IAM policies and identify over-permissioned principals or stale bindings. Cloud Resource Manager pairs search endpoints with getIamPolicy on every container, giving compliance teams a single source for hierarchy-wide access reviews without scraping the console.
Iterate through every project in organizations/9999 and return any binding granting roles/owner to a non-corporate identity
Tag-Driven Cost Allocation
Apply tag keys and tag values to projects and folders so billing exports and policy controls can group spend by team, product, or environment. Cloud Resource Manager creates tag bindings programmatically, letting finance and platform teams roll out a consistent tagging taxonomy across thousands of projects without manual click-ops.
Create tag value tagValues/cost-center-42 under tag key environment and bind it to project projects/acme-prod-eu
Agent-Driven Landing Zone Setup
An AI agent invoked through Jentic can stand up a complete landing zone by calling Cloud Resource Manager to create the folder structure, provision projects, and apply baseline IAM and tag policies. Because Jentic returns the operation schema directly, the agent does not need to crawl Google's discovery docs to build each request.
Use Jentic to search 'create gcp project', load the projects.create schema, and provision three projects under folders/dev, folders/stage, and folders/prod
Key Endpoints
28 endpoints — the cloud resource manager api creates, reads, and updates metadata for google cloud platform resource containers including projects, folders, organizations, tag keys, and tag values.
METHOD
PATH
DESCRIPTION
POST
/v3/projects
Create a new GCP project
GET
/v3/projects:search
Search projects accessible to the caller
GET
/v3/folders
List folders under a parent
POST
/v3/folders
Create a folder in the resource hierarchy
GET
/v3/effectiveTags
Look up effective tags inherited on a resource
POST
/v3/liens
Place a lien to block project deletion
POST
/v3/projects
Create a new GCP project
GET
/v3/projects:search
Search projects accessible to the caller
GET
/v3/folders
List folders under a parent
POST
/v3/folders
Create a folder in the resource hierarchy
GET
/v3/effectiveTags
Look up effective tags inherited on a resource
POST
/v3/liens
Place a lien to block project deletion
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
Cloud Resource Manager API
- Foundational (D-)41/100
70
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
70
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: A-Signals: 4
81%
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).
100%
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: B-Signals: 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 Cloud Resource Manager API by hand means setting up Google OAuth 2.0, minting short-lived tokens against the cloud-platform scope, and addressing projects and folders by resource name against cloudresourcemanager.googleapis.com yourself. Through Jentic you install once, import the Cloud Resource Manager API from the API Directory, store the OAuth credential once, and your agent calls it.
Permission scoping
Cloud Resource Manager puts the project and folder resource names in the URL path (/v3/{+name}, /v3/{+name}:move), so a rule can pin your agent to one folder: it can search and create projects under it and nothing else. You choose the operations it may call, so move, undelete, or setIamPolicy are not included unless you add them.
Credential isolation
Your Cloud Resource Manager OAuth credential is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'create a GCP project' or 'set an IAM policy on a folder', and Jentic returns the matching Resource Manager operation with its input 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 Cloud Resource Manager API through Jentic.
What authentication does the Cloud Resource Manager API use?
It uses Google OAuth 2.0 with scopes such as https://www.googleapis.com/auth/cloud-platform and https://www.googleapis.com/auth/cloud-platform.read-only. Through Jentic, the OAuth refresh token and client secret are stored in your Jentic One instance and never exposed to the agent runtime.
Can I create new GCP projects with the Cloud Resource Manager API?
Yes. Send a POST to /v3/projects with the parent folder or organization, a project ID, and a display name. The endpoint returns a long-running operation that you can poll until the project is fully provisioned.
What are the rate limits for the Cloud Resource Manager API?
Google enforces per-project read and write quotas on Resource Manager, with mutating operations like project creation and IAM policy updates limited far more aggressively than reads. Run heavy hierarchy scans against the search endpoints with backoff and request quota increases for large landing-zone rollouts.
How do I apply tag bindings to a project through Jentic?
Search Jentic for 'apply tag binding to gcp project', load the tagBindings.create schema, and execute a call against /v3/tagBindings with the parent project resource name and the tag value. Jentic returns the input schema so the agent can fill the required fields without reading Google's discovery doc.
Is the Cloud Resource Manager API free?
The API itself has no per-call charge - you only pay for the underlying Google Cloud resources you create. Quota limits apply at the project level even when usage is free.
How does the API handle deletion protection?
Place a lien on a project via /v3/liens to block deletion until the lien is removed. Liens are useful guard rails when an agent or CI pipeline has broad project-write permissions but you want explicit confirmation before destructive actions.
Can I limit what my agent is allowed to do with the Cloud Resource Manager API?
Yes. Because you self-host Jentic One, your own rules decide which Cloud Resource Manager operations and OAuth credential the agent may use. Since the API puts project and folder resource names in the URL path (for example /v3/{+name} and /v3/{+name}:move), you can pin the agent to a single folder so it can only search and create projects under it. You choose the operations it may call, so sensitive actions like move, undelete, and setIamPolicy stay unavailable unless you explicitly add them.
GET STARTED