Service Consumer Management API

Name: Service Consumer Management API API
Brand: Service Consumer Management API
Availability: InStock

✓ Official Vendor SpecCloud InfrastructureNetworkingoauth212 EndpointsREST

For Agents

Programmatically provision and manage per-consumer tenant projects for services built on Google's Service Infrastructure.

Quickstart

Get started with Service Consumer Management 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:
"create a tenant project for a service consumer"

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

Capabilities

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

GET STARTED

Start building with Service Consumer Management API API

Explore with Jentic

View OpenAPI Document

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.

Use Cases

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

Why though Jentic?

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

Credential isolation

Producer-side GCP service account credentials are stored encrypted in the Jentic MAXsystem vault. Agents receive a short-lived scoped access token at execution and never see the producer's long-lived key material.

Intent-based discovery

Agents search Jentic by intent (e.g. 'add a tenant project to a tenancy unit') and Jentic returns the matching tenancyUnits.addProject operation with its full input schema, so the agent does not have to navigate the producer-only documentation.

Time to first call

Direct integration: 3-5 days to wire up producer credentials, long-running operation polling, and tenant baseline configuration. Through Jentic: under 1 hour — search, load, execute, with operation polling handled at the SDK layer.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

Google Service Management API

Producers register and manage their service definitions with Service Management; Service Consumer Management handles the per-consumer tenancy on top.

Use Service Management to publish a service. Use Service Consumer Management to provision tenant projects for that service.

Complementary

Google Cloud Resource Manager API

Manages GCP organizations, folders, and projects — the underlying primitives that tenant projects sit on.

Use Resource Manager for direct project lifecycle. Use Service Consumer Management when project lifecycle is wrapped in a service-tenancy abstraction.

Complementary

Google Service Usage API

Enables and disables Google services on a project, including tenant projects under management.

Use Service Usage to flip services on or off inside a tenant project. Use Service Consumer Management to manage the tenant project itself.

Alternative

Google Cloud IAM API

Manages service accounts and roles directly, an alternative to letting applyProjectConfig handle IAM bindings.

Use IAM API for fine-grained role and service account work. Use Service Consumer Management when IAM is part of a tenant baseline config.

FAQs

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