Google Service Usage API
Browse all Google APIs43
AI ReadinessFoundational (D)43/100
Official vendor OpenAPI document · agent-readyCloud InfrastructureNetworkingoauth29 EndpointsREST
For Agents
List, enable, and disable Google Cloud services on a project, folder, or organization in bulk or one at a time.
Use for: Enable the Cloud Run API on my project, List every service currently enabled on a project, Disable an unused API to reduce attack surface, Batch enable 10 APIs needed for a new microservice
Not supported: Does not handle project creation, IAM role assignment, or quota requests - use for listing and toggling Google service enablement on a project only.
Service Usage is the consumer-side API for managing which Google Cloud services are enabled on a project, folder, or organization. Agents can list every available service in the catalogue, see which are currently enabled, enable or disable a service, and batch enable up to 20 services in one call. It is the API behind 'Enable APIs and services' in the GCP console and the foundation for any tooling that bootstraps GCP projects.
Install Jentic One Beta
Connect the Service Usage API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Service Usage 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%2Fserviceusage" | 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%2Fserviceusage" | 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 Service Usage API.
List every Google service available to a parent (project, folder, or organization) with current enablement state
Enable a single service on a project to make its API callable
Disable a single service on a project to remove its API access
Batch enable up to 20 services on a project in one call
Retrieve metadata for a specific service including its config and dependencies
Cancel and read long-running enablement operations
Use Cases
Patterns agents use Service Usage API for, with concrete tasks.
★ GCP Project Bootstrap Automation
Tools that create new GCP projects programmatically use Service Usage to enable the right APIs (compute, run, sql-admin, secretmanager, monitoring, etc.) right after project creation. The batchEnable endpoint accepts up to 20 services per call, so a typical bootstrap finishes in a single round-trip plus operation polling.
Call POST /v1/{+parent}/services:batchEnable with serviceIds=['compute.googleapis.com','run.googleapis.com','secretmanager.googleapis.com'] and poll the returned operation.
Security Posture and Surface Reduction
Periodically list enabled services on every project and disable any that are unused, reducing the attack surface and IAM blast radius. Pair Service Usage with Cloud Audit Logs to identify services with no activity over the last 90 days, then call disable on each one.
List services with filter='state:ENABLED', cross-reference Cloud Audit Logs, then call POST on each unused service's name with :disable.
Pre-flight Capability Checks
Before running automation that depends on a particular API, tools call services.get to confirm the service is enabled and bail out cleanly if not. This avoids opaque permission errors deeper in the workflow and gives a clear remediation message - 'enable the X API on this project'.
Call GET /v1/{+name} on projects/{project}/services/run.googleapis.com and assert the response state equals ENABLED before proceeding.
AI Agent GCP Onboarder
An AI agent acts as a GCP onboarding assistant - given a project id and a target workload type, it figures out which services are needed, batch enables them, and surfaces any quota or billing prerequisites. Through Jentic the agent searches by intent and never holds the long-lived service account credentials directly.
Given workloadType='ml-inference', batch enable aiplatform, run, storage, and secretmanager, then poll the operation and report any billing-disabled errors.
Key Endpoints
9 endpoints — service usage is the consumer-side api for managing which google cloud services are enabled on a project, folder, or organization.
METHOD
PATH
DESCRIPTION
GET
/v1/{+parent}/services
List every Google service for a parent
POST
/v1/{+parent}/services:batchEnable
Batch enable up to 20 services
POST
/v1/{+name}:enable
Enable a single service on a project
POST
/v1/{+name}:disable
Disable a service on a project
GET
/v1/{+name}
Get details and state of a single service
POST
/v1/{+name}:cancel
Cancel a long-running enablement operation
GET
/v1/{+parent}/services
List every Google service for a parent
POST
/v1/{+parent}/services:batchEnable
Batch enable up to 20 services
POST
/v1/{+name}:enable
Enable a single service on a project
POST
/v1/{+name}:disable
Disable a service on a project
GET
/v1/{+name}
Get details and state of a single service
POST
/v1/{+name}:cancel
Cancel a long-running enablement operation
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.
S
Service Usage API
- Foundational (D)43/100
49
Foundational Compliance56
Developer Experience & Jentic Compatibility21
AI-Readiness & Agent Experience94
Agent Usability63
Security68
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
49
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: D+Signals: 4
72%
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).
25%
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.
21
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: FSignals: 4
85%
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).
68
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: B+Signals: 1
68%
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 Google Service Usage by hand means setting up a service account, minting OAuth access tokens against serviceusage.googleapis.com, and looking up canonical service names yourself. Through Jentic you install once, import the Service Usage API from the API Directory, store the OAuth credential once, and your agent calls it.
Permission scoping
Service Usage puts the project and service in the URL path (/v1/{name}:enable, /v1/{name}:disable), so a rule can pin your agent to one project: it can list and enable services there and nothing else. You choose the operations it may call, so disable is not included unless you add it.
Credential isolation
Your Service Usage 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 'enable Cloud Run on a project' or 'list enabled services', and Jentic returns the matching Service Usage 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 Service Usage API through Jentic.
What authentication does the Service Usage API use?
Service Usage uses OAuth 2.0 with the cloud-platform scope and IAM permissions like roles/serviceusage.serviceUsageAdmin on the project, folder, or organization. Through Jentic the credentials are stored encrypted in your Jentic One instance and a scoped token is provided at execution.
How many services can I batch enable at once?
Up to 20 service IDs in a single POST /v1/{+parent}/services:batchEnable call. For larger sets, split into batches and poll each returned long-running operation to completion.
What are the rate limits for the Service Usage API?
Google enforces a default per-project quota of 600 read requests per minute and 60 write requests per minute. Enable and disable actions are long-running operations because they involve provisioning IAM service agents and quota allocations.
How do I enable an API through Jentic?
Run the Jentic search query 'enable a google cloud service on a project', load POST /v1/{+name}:enable, and execute it with the service resource name like projects/{project}/services/run.googleapis.com. Jentic handles the OAuth token and operation polling.
Can I enable services at the folder or organization level?
List and get operations support folder and organization parents. Enable and disable target a specific project; folder- and organization-level enablement is handled through organization policies rather than this API.
Will disabling a service delete its data?
Disabling stops API calls from succeeding but does not delete underlying resources or data created via that API. Re-enabling the service restores access to existing resources, subject to any retention windows the service itself enforces.
Can I limit what my agent is allowed to do with the Service Usage API?
Yes. Because Service Usage puts the project and service in the URL path, your self-hosted Jentic One instance lets you write rules that pin the agent to a single project, so it can list and enable services there and nothing else. You choose exactly which operations it may call, so a destructive action like disable stays off unless you explicitly add it. The OAuth credential is stored by your own instance and injected only at execution, so the agent never holds it directly.
GET STARTED