Google Cloud Billing API
Browse all Google APIs39
AI ReadinessNon-Ready (F)39/100
Official vendor OpenAPI document · agent-readyFinanceAccountingoauth218 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.
Use for: I need to attach my new project to our shared billing account, List every billing account our organization can access, Move a project to a different billing account before month end, Find which billing account funds a given Google Cloud project
Not supported: Does not return invoices, per-resource cost lines, or budget alerts - use for billing-account, project-link, and SKU catalog management only.
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. Agents can enumerate every billable service and SKU in the catalog, look up the billing account a project is attached to, and move projects or sub-accounts between billing accounts. The API also exposes IAM policy management on billing accounts so that finance and platform teams can grant or audit billing administrator access programmatically.
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.
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%2Fcloudbilling" | 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%2Fcloudbilling" | 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 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
Enumerate the public catalog of Google Cloud services and SKUs
Read or update IAM policies that control who can manage a billing account
Create sub-accounts under a master billing account for resale or cost separation
Look up the billing account currently linked to a specific project
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
GET
/v1/{+name}/projects
List projects attached to a billing account
POST
/v1/{+name}:move
Move a billing sub-account to a new parent
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.
C
Cloud Billing API
- Non-Ready (F)39/100
63
Foundational Compliance56
Developer Experience & Jentic Compatibility17
AI-Readiness & Agent Experience94
Agent Usability63
Security67
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
63
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: B-Signals: 4
77%
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).
75%
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.
17
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: FSignals: 4
68%
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).
67
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: BSignals: 1
67%
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 the Cloud Billing API by hand means setting up Google Cloud OAuth or a service account, minting cloud-billing scoped tokens, and coordinating billing-account, project-link, and SKU catalog calls yourself. Through Jentic you install once, import the Cloud Billing API from the API Directory, store the credential once, and your agent calls it.
Permission scoping
The API puts the billing account and project in the URL path (/v1/{+name}/billingInfo, /v1/{+name}/projects), so a rule can pin your agent to one billing account: it can read and link projects there and nowhere else. You choose the operations it may call, so ones like moving a billing account are not included unless you add them.
Credential isolation
Your Google Cloud OAuth credentials or service account key are stored once, encrypted, by your own Jentic One instance and injected at execution time. The agent receives only short-lived cloud-billing scoped tokens and the service account JSON never enters its prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'link a GCP project to a billing account', and Jentic returns the matching Cloud Billing operation with its parameter 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 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 your Jentic One instance 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.
Can I limit what my agent is allowed to do with the Cloud Billing API?
Yes. Because you run Jentic One yourself and write the rules, you decide which Cloud Billing operations the agent may call and which credential it uses. Since the billing account and project sit in the URL path (for example /v1/{name}/billingInfo and /v1/{name}/projects), a rule can pin the agent to a single billing account so it can list and link projects there and read the public service and SKU catalog, and nothing else. Sensitive operations such as moving a sub-account to a new parent or updating IAM policies are excluded unless you explicitly allow them.
GET STARTED