Google Service Consumer Management API

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

✓ Official Vendor SpecCloud InfrastructureNetworkingoauth212 Endpoints

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.

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

GET STARTED

Start building with Service Consumer Management API

Explore with Jentic

View OpenAPI Document

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.

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

Why Jentic?

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

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.

Time to first call

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.

Google Service Consumer Management API

Connect the Service Consumer Management API to your agent

Capabilities

Start building with Service Consumer Management API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs