Google Cloud Billing API

Name: Cloud Billing API
Brand: Cloud Billing API
Availability: InStock

✓ Official Vendor SpecFinanceAccountingoauth218 EndpointsREST

For Agents

Manage Google Cloud billing accounts, project-to-account associations, and the public service and SKU catalog. Useful for cost-attribution, account hygiene, and finance automation on GCP.

Install Jentic One Beta

Connect the Cloud Billing API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Cloud Billing 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 Cloud Billing API.

List and read every billing account a caller has access to

Attach or detach a Google Cloud project from a billing account

Move a project or sub-account to a different billing account

GET STARTED

Start building with Cloud Billing API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Cloud Billing API for, with concrete tasks.

★ Project-to-Billing-Account Hygiene

Platform teams use the Cloud Billing API to keep every Google Cloud project linked to the right billing account. The updateBillingInfo operation moves a project to a new account, and listProjectBillingInfo enumerates current associations. This is the basis for chargeback workflows that require every project to roll up to a known cost centre.

Call PUT /v1/{name}/billingInfo with name=projects/my-project and billingAccountName=billingAccounts/01ABCD-234567-89EFGH

Channel Partner Sub-Account Provisioning

Resellers and managed service providers use the Cloud Billing API to create sub-accounts under a master billing account so each customer's spend is isolated. Sub-accounts inherit credit terms from the master account but produce separate invoices, which simplifies billback and reporting.

Call POST /v1/{parent}/billingAccounts with parent=billingAccounts/01ABCD-234567-89EFGH and a displayName for the new sub-account

Service and SKU Catalog Enumeration

Cost-modelling tools call the public services and skus endpoints to pull the full Google Cloud catalog — every service, every SKU, with pricing tiers and units. This drives cost estimators, what-if analyses, and FinOps dashboards without scraping the public price list.

Call GET /v1/services to list services, then GET /v1/{parent}/skus on the Compute Engine service name to enumerate its SKUs

AI Agent Billing Auditor via Jentic

An agent uses the Cloud Billing API to answer finance questions on demand: which projects are unlinked, who has billing admin on the master account, what new SKUs were added this week. Through Jentic, the agent loads the operation schema, runs the call against the configured organization, and reports back with structured evidence.

Search Jentic for 'list google cloud billing accounts', execute the operation, then for each result call GET /v1/{name}/projects and flag unlinked projects

Key Endpoints

18 endpoints — the google cloud billing api lets developers manage billing accounts, link or unlink projects from a billing account, and read the public catalog of google cloud services and skus.

METHOD

PATH

DESCRIPTION

GET

/v1/billingAccounts

List billing accounts the caller can access

POST

/v1/billingAccounts

Create a new billing account or sub-account

GET

/v1/{+name}/billingInfo

Get the billing account linked to a project

PUT

/v1/{+name}/billingInfo

Attach or detach a project from a billing account

GET

/v1/services

List Google Cloud services in the public catalog

GET

/v1/{+name}/projects

List projects attached to a billing account

POST

/v1/{+name}:move

Move a billing sub-account to a new parent

GET

/v1/billingAccounts

List billing accounts the caller can access

POST

/v1/billingAccounts

Create a new billing account or sub-account

GET

/v1/{+name}/billingInfo

Get the billing account linked to a project

PUT

/v1/{+name}/billingInfo

Attach or detach a project from a billing account

GET

/v1/services

List Google Cloud services in the public catalog

Why Jentic?

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

Credential isolation

Google Cloud OAuth 2.0 credentials and service account keys are stored encrypted in the Jentic vault. Agents receive short-lived access tokens scoped to cloud-billing — raw service account JSON never enters the agent context.

Intent-based discovery

Agents search Jentic by intent (e.g. 'link gcp project to billing account') and Jentic returns the matching Cloud Billing operation with its parameter schema, so the agent can call the right endpoint without reading Discovery docs.

Time to first call

Direct Cloud Billing integration: 1-2 days for OAuth, scope selection, and resource-name handling. Through Jentic: under an hour — search, load schema, execute.

FAQs

Specific to using Cloud Billing API through Jentic.

What authentication does the Cloud Billing API use?

The Cloud Billing API uses OAuth 2.0 with the cloud-platform or cloud-billing scope. Tokens are issued for a Google service account or end user. Through Jentic, the OAuth credential lives in the Jentic vault and the agent receives a short-lived access token only — the underlying service account key never enters agent context.

Can I move a project to a different billing account with this API?

Yes. PUT /v1/{name}/billingInfo with name set to projects/PROJECT_ID and a body that sets billingAccountName to the target billing account resource. The caller needs billing.resourceAssociations.create on the target account and the same permission to detach from the old one.

What are the rate limits for the Cloud Billing API?

Cloud Billing API quotas are published per-method in the Google Cloud console under the Cloud Billing API quota page; typical defaults are several thousand requests per minute per project for the read-heavy services and skus endpoints, with lower limits for write operations on billing accounts.

How do I list every project tied to a billing account through Jentic?

Search Jentic for 'list projects on google cloud billing account' and execute the resulting operation against GET /v1/{name}/projects with name=billingAccounts/01ABCD-234567-89EFGH. The response is a paginated list of ProjectBillingInfo entries.

Does the Cloud Billing API expose actual cost data?

No. The Cloud Billing API manages billing-account metadata and the public SKU catalog; it does not return invoices or per-resource cost line items. For consumed cost data, export billing data to BigQuery and query it from there, or use Cloud Billing's BigQuery Export feature.

Is the Cloud Billing API free?

The Cloud Billing API itself has no per-call charge. Standard Google Cloud usage and the BigQuery storage and query charges that come with billing exports are billed normally as documented on the Google Cloud pricing page.

Google Cloud Billing API

Connect the Cloud Billing API to your agent

Capabilities

Start building with Cloud Billing API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs