Google Service Consumer Management API
Browse all Google APIs42
AI ReadinessFoundational (D-)42/100
Official vendor OpenAPI document · agent-readyCloud InfrastructureNetworkingoauth212 EndpointsREST
For Agents
Programmatically provision and manage per-consumer tenant projects for services built on Google's Service Infrastructure.
Use for: Create a new tenant project for a customer onboarding to my managed service, Attach an existing customer project as a tenant under my service, Apply IAM bindings and billing config to a freshly provisioned tenant project, Remove a tenant project after a customer cancels
Not supported: Does not handle service definition publishing, end-user authentication, or workload deployment - use for producer-side tenant project provisioning and lifecycle only.
Service Consumer Management is the Google Cloud API service producers use to manage tenant projects and tenancy units for services built on Service Infrastructure. It lets producers create per-consumer tenant projects, attach existing projects, apply project-level configuration like IAM bindings and billing accounts, and clean up by detaching, removing, or undeleting projects. This is the control plane behind multi-tenant SaaS-on-GCP offerings such as Cloud SQL or AlloyDB private services.
Install Jentic One Beta
Connect the Service Consumer Management API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Service Consumer Management 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%2Fserviceconsumermanagement" | 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%2Fserviceconsumermanagement" | 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 Consumer Management API.
Create and search tenancy units associated with a service and consumer
Add and remove tenant projects within a tenancy unit, including dedicated and shared modes
Attach existing GCP projects as tenant projects on a tenancy unit
Apply project-level configuration (IAM, billing, services) to attached tenant projects
Delete or undelete tenant projects to manage consumer offboarding and recovery
Track long-running operations for asynchronous tenancy actions
Use Cases
Patterns agents use Service Consumer Management API for, with concrete tasks.
★ Multi-Tenant SaaS Provisioning on GCP
Service producers building managed offerings on top of GCP (private databases, dedicated networks, regulated workloads) use Service Consumer Management to spin up an isolated tenant project per customer, apply baseline IAM and billing config, and tear it down when the customer leaves. The API replaces ad-hoc Resource Manager + Billing + IAM scripts with a single tenancy-unit abstraction.
Call POST /v1/{+parent}/tenancyUnits:addProject with a tenant project config that sets billingConfig.billingAccount and an IAM policy for the customer's service account.
Customer Offboarding Cleanup
When a customer leaves, automation walks the tenancy unit, removes each tenant project, and cancels any in-flight long-running operations. Service Consumer Management exposes deleteProject, removeProject, and undeleteProject so the workflow is auditable and reversible if a project is removed in error.
Call POST /v1/{+name}:removeProject for each tenant project in the tenancy unit, then poll the returned operations until done=true.
Tenant Configuration Refresh
Periodically reapply baseline configuration (services enabled, IAM bindings, audit log settings) across every tenant project to enforce policy drift back to a known-good state. The applyProjectConfig action is idempotent and supports drift correction without recreating the project.
Call POST /v1/{+name}:applyProjectConfig with the standard tenant config for every tenancy unit returned by tenancyUnits.list.
AI Agent Tenancy Operator
An AI agent runs the on-call tenancy operations for a managed-service team - provisioning new tenants, retrying failed apply operations, and answering 'where is project X?' from chat. Through Jentic the agent searches by intent and never holds the producer's service account credentials directly.
On chat command, call tenancyUnits:addProject for the named customer, watch the long-running operation, then post the resulting tenant project id back to the channel.
Key Endpoints
12 endpoints — service consumer management is the google cloud api service producers use to manage tenant projects and tenancy units for services built on service infrastructure.
METHOD
PATH
DESCRIPTION
POST
/v1/{+parent}/tenancyUnits
Create a tenancy unit
POST
/v1/{+parent}/tenancyUnits:search
Search tenancy units for a service and consumer
POST
/v1/{+name}:addProject
Add a tenant project to a tenancy unit
POST
/v1/{+name}:attachProject
Attach an existing project as a tenant project
POST
/v1/{+name}:applyProjectConfig
Apply baseline configuration to a tenant project
POST
/v1/{+name}:removeProject
Remove a tenant project from a tenancy unit
POST
/v1/{+parent}/tenancyUnits
Create a tenancy unit
POST
/v1/{+parent}/tenancyUnits:search
Search tenancy units for a service and consumer
POST
/v1/{+name}:addProject
Add a tenant project to a tenancy unit
POST
/v1/{+name}:attachProject
Attach an existing project as a tenant project
POST
/v1/{+name}:applyProjectConfig
Apply baseline configuration to a tenant project
POST
/v1/{+name}:removeProject
Remove a tenant project from a tenancy unit
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 Consumer Management API
- Foundational (D-)42/100
49
Foundational Compliance56
Developer Experience & Jentic Compatibility21
AI-Readiness & Agent Experience94
Agent Usability63
Security58
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
71%
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
84%
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).
58
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: C+Signals: 1
58%
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 Consumer Management by hand means provisioning a producer service account, minting OAuth access tokens against serviceconsumermanagement.googleapis.com, and refreshing them yourself. Through Jentic you install once, import the Service Consumer Management API from the API Directory, store the OAuth credential once, and your agent calls it.
Permission scoping
Service Consumer Management puts the tenancy unit in the URL path (/v1/{name}:addProject, /v1/{name}:removeProject), so a rule can pin your agent to one tenancy unit: it can search and add projects there and nothing else. You choose the operations it may call, so removeProject is not included unless you add it.
Credential isolation
Your Service Consumer Management 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 'add a tenant project to a tenancy unit' or 'search tenancy units', and Jentic returns the matching Service Consumer Management 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 Consumer Management API through Jentic.
What authentication does the Service Consumer Management API use?
It uses OAuth 2.0 with the cloud-platform scope and producer-side IAM permissions like roles/servicemanagement.serviceController on the producer service. Through Jentic the OAuth credentials are stored encrypted in your Jentic One instance and a scoped token is provided at execution.
Who is this API for - service producers or consumers?
It is the producer-side control plane. If you are publishing a managed service on GCP, you use this API to create and manage tenant projects per customer. End consumers do not call it directly.
What are the rate limits for the Service Consumer Management API?
Google enforces a default per-project quota of 60 write operations per minute and 600 read operations per minute. Many tenant operations are long-running, so the practical throughput is bounded by GCP project provisioning latency rather than the API quota.
How do I attach an existing customer project through Jentic?
Run the Jentic search query 'attach a tenant project in service consumer management', load POST /v1/{+name}:attachProject, and execute it with the externalResource pointing at the customer's project number. Jentic injects the producer service account token.
Can I undo a tenant project removal?
Yes, within the GCP undelete window. Call POST /v1/{+name}:undeleteProject on the tenant project resource. After the window expires the project is permanently deleted and cannot be restored via the API.
Why are most write operations long-running?
Tenant project creation, attachment, and config apply involve provisioning Resource Manager projects, billing links, and IAM bindings. The API returns an Operation; callers poll GET /v1/{+name} on the operations resource until done=true.
Can I limit what my agent is allowed to do with the Service Consumer Management API?
Yes. Jentic One is self-hosted, so your own rules decide which Service Consumer Management operations and credentials your agent can use. Because the API puts the tenancy unit in the URL path, you can pin the agent to a single tenancy unit and let it call only the operations you allow, such as searching tenancy units and running addProject or applyProjectConfig. Destructive calls like removeProject or deleteProject stay out of reach unless you explicitly add them, and the OAuth credential is injected at execution rather than exposed to the agent.
GET STARTED