Service Usage API

Name: Service Usage API API
Brand: Service Usage API
Availability: InStock

✓ Official Vendor SpecCloud InfrastructureNetworkingoauth29 EndpointsREST

For Agents

List, enable, and disable Google Cloud services on a project, folder, or organization in bulk or one at a time.

Quickstart

Get started with Service Usage API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"enable a google cloud service on a project"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Service Usage API 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

GET STARTED

Start building with Service Usage API API

Explore with Jentic

View OpenAPI Document

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.

Use Cases

Patterns agents use Service Usage API 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

Why though Jentic?

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

Credential isolation

GCP service account credentials and OAuth tokens are stored encrypted in the Jentic MAXsystem vault. Agents call Service Usage with a short-lived scoped access token and never see the long-lived key material that bootstraps projects.

Intent-based discovery

Agents search Jentic by intent (e.g. 'enable cloud run on a project') and Jentic returns the matching services:enable operation with its full schema, so the agent does not have to look up canonical service names by hand.

Time to first call

Direct integration: 1-2 days to wire enable, batchEnable, and operation polling into a project-bootstrap script. Through Jentic: under 30 minutes — search, load, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

Google Cloud Resource Manager API

Manages projects, folders, and organizations — the parents that Service Usage operates on.

Use Resource Manager for the project lifecycle. Use Service Usage to enable APIs once the project exists.

Complementary

Google Cloud IAM API

Manages service accounts and roles, including the IAM service agents created when an API is enabled.

Use IAM to manage roles and service accounts. Use Service Usage to control which APIs each project can call.

Alternative

Google Service Management API

The producer-side counterpart for publishing services that consumers later enable via Service Usage.

Use Service Management as a producer. Use Service Usage as a consumer.

Complementary

Google Service Consumer Management API

Producer-side API for managing tenant projects whose services are enabled via Service Usage.

Use Service Consumer Management for producer tenancy. Use Service Usage for consumer enablement.

FAQs

Specific to using Service Usage API 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 MAXsystem 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.