Google Service Usage API

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

✓ Official Vendor SpecCloud InfrastructureNetworkingoauth29 EndpointsREST

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.

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 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

GET STARTED

Start building with Service Usage API

Explore with Jentic

View OpenAPI Document

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.

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

Why 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.

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 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.

Google Service Usage API

Connect the Service Usage API to your agent

Capabilities

Start building with Service Usage API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs