Jentic OSThe workplace. An in-house AI platform for every employeeJentic OneSafe access. Agents reach your systems without holding keysJentic AIRThe foundation. Gets your existing platforms ready for AI
Pricing

GET STARTED

API DirectoryBrowse 10,000+ APIs ready for AI agent integrationDocumentationGuides and API reference

TOOLS

API ScoringCheck your AI readiness using our scorecardArazzo UIVisualize Arazzo workflows as interactive documentationArazzo EditorBuild and edit multi-step API workflows visually

COMMUNITY

GitHubOpen source projects and examplesOpen StandardsBuilt on open specs. Never locked in.
All ResourcesEverything in one placeBlogLatest articles and insightsTech Talk NewsletterAPIs, AI agents, architecture and strategyWebinarsLive sessions and on-demand recordingsReports & WhitepapersOriginal research on enterprise AI
About UsOur mission and teamCareersJoin our teamContactGet in touch
Try it now
Jentic OSJentic OneJentic AIR
Pricing
API DirectoryDocumentationAPI ScoringArazzo UIArazzo EditorGitHubOpen Standards
All ResourcesBlogTech Talk NewsletterWebinarsReports & Whitepapers
About UsCareersContact
Try it now
JenticJentic
Products
  • Jentic OS
  • Jentic One
  • Jentic AIR
For Developers
  • API Directory
  • Documentation
  • GitHub
Company
  • About Jentic
  • Careers
  • Contact Us
  • Trust Centre
ISO/IEC 27001:2022 certification badge issued by Prescient SecurityISO/IEC 27001:2022 certification badge issued by Prescient Security

Information Security Management System

Certified to ISO/IEC 27001:2022 by Prescient Security

AICPA SOC for Service Organizations logoAICPA SOC for Service Organizations logo

SOC 2® Type 1 report

Audited by Prescient Assurance

Terms & Conditions•Privacy Policy•
© 2026 Jentic Technology Ltd. All rights reserved.
2 Grattan Court East, Dublin, D02 VX86, Ireland
Switch to light modeSwitch to dark mode
APIs / Finance / Google / Cloud Billing Budget API
Cloud Billing Budget API logo

Google Cloud Billing Budget API

Browse all Google APIs
39
AI ReadinessNon-Ready (F)39/100
See full scorecard
Official vendor OpenAPI document · agent-readyFinanceExpense Managementoauth25 EndpointsREST

For Agents

Create and manage Cloud Billing budgets, threshold rules, and notification settings for a billing account. Agents can list budgets, patch thresholds, and inspect spend filters.

Use for: I need to create a budget of $5,000 a month for project myproj, List all budgets on a Cloud Billing account, Get the threshold rules attached to a specific budget, Update the alert thresholds on an existing budget

Not supported: Does not block spend, manage billing accounts, or run cost reports - use for budget creation, threshold alerts, and Pub/Sub notification wiring only.

The Cloud Billing Budget API stores spending budgets attached to a Cloud Billing account and the threshold rules that fire as spend accrues against that plan. You can create budgets scoped to whole billing accounts, specific projects, services, or labels, and configure alert thresholds at percentage triggers. Budgets are FinOps guardrails - not enforcement. They emit notifications via Cloud Pub/Sub or email so other systems can react, but they do not stop resource provisioning. Use them to track and alert on Google Cloud spend.

Jentic One on GithubView OpenAPI Document

Install Jentic One Beta

Connect the Cloud Billing Budget API to your agent

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

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%2Fbillingbudgets" | 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 Budget API.

Create budgets scoped to a billing account, projects, services, or labels

Configure threshold rules at percentage points of forecasted or actual spend

List budgets under a billing account and inspect their filters

Patch a budget's amount, filter, or threshold rules without recreating it

Delete budgets that are no longer needed

Wire budget notifications to a Pub/Sub topic or notification channel

Use Cases

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

★ Project-Level Spend Alerts

Create a budget per environment so spend on dev, staging, and prod each fire at their own thresholds. Budgets are managed at /v1/{parent}/budgets with a billing account parent and a budgetFilter containing projects[]. Threshold rules at 50/75/90/100 percent trigger emails to billing admins or Pub/Sub messages for downstream automation.

Create a $5,000 monthly budget on billingAccounts/012345-678901-23ABCD scoped to projects/myproj-dev with thresholds at 50, 75, 90 percent.

Service Cost Tracking

Filter budgets by service (BigQuery, Compute Engine, Cloud Storage) to track per-service spend across the org. budgetFilter.services accepts service IDs and combines with projects, labels, and creditTypes for fine-grained scoping. Useful for FinOps teams who chargeback by service.

Create a budget that filters services to BigQuery and Compute Engine across all projects under billingAccount 012345-678901-23ABCD with a $20,000 monthly cap.

Pub/Sub-Driven Automation

Configure notificationsRule.pubsubTopic on a budget so percentage thresholds emit JSON messages that other systems consume. Combined with Cloud Functions or Workflows, this enables automated cost responses such as scaling down non-prod resources when spend crosses 80 percent.

Patch existing budget budgets/abc to add notificationsRule with pubsubTopic projects/myproj/topics/billing-alerts.

Agent-Driven FinOps Setup

An AI agent takes a request like 'put a $10k cap on the analytics project with alerts at 80 and 100 percent' and creates the budget through Jentic. The agent loads the create operation, applies the right filter and thresholds, and reports back the budget resource name. OAuth tokens stay in your Jentic One instance.

Given the request 'cap analytics project at $10k with alerts at 80 and 100 percent', create a budget scoped to projects/analytics with the right thresholdRules.

Key Endpoints

5 endpoints — the cloud billing budget api stores spending budgets attached to a cloud billing account and the threshold rules that fire as spend accrues against that plan.

METHOD

PATH

DESCRIPTION

POST

/v1/{+parent}/budgets

Create a budget on a billing account

GET

/v1/{+parent}/budgets

List budgets on a billing account

GET

/v1/{+name}

Get a single budget

PATCH

/v1/{+name}

Update an existing budget

DELETE

/v1/{+name}

Delete a budget

POST

/v1/{+parent}/budgets

Create a budget on a billing account

GET

/v1/{+parent}/budgets

List budgets on a billing account

GET

/v1/{+name}

Get a single budget

PATCH

/v1/{+name}

Update an existing budget

DELETE

/v1/{+name}

Delete a budget

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

- Non-Ready (F)
39/100
65
Foundational Compliance
56
Developer Experience & Jentic Compatibility
16
AI-Readiness & Agent Experience
94
Agent Usability
63
Security
63
AI Discoverability
Powered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
65

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: BSignals: 4
85%

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.

16

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: FSignals: 4
66%

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

63

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: B-Signals: 1
62%

Descriptive Richness

Clarity and depth of descriptions across API elements.

View full reportHow the score is calculatedMore about the dimensions

Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

Score your own APIScoring CLI agent skill
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 Budget API by hand means standing up its Google OAuth 2.0 flow, refreshing scoped access tokens, and assembling budgetFilter and thresholdRules payloads with Pub/Sub notification wiring yourself. Through Jentic you install once, import the Cloud Billing Budget API from the API Directory, store the OAuth credentials once, and your agent calls it.

Permission scoping

The API puts the billing account and budget in the URL path (/v1/{+parent}/budgets and /v1/{+name}), so a rule can pin your agent to one billing account's budgets: it can create budgets and read their thresholds there and nowhere else. You choose the operations it may call, so deleting a budget is not included unless you add it.

Credential isolation

Your Google OAuth client credentials and refresh token are stored once, encrypted, by your own Jentic One instance and injected at execution time. The agent receives only short-lived scoped access tokens and never sees the refresh token in its prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'create a GCP budget with a 90 percent alert', and Jentic returns the create budget operation with its budgetFilter and thresholdRules schema so the agent calls the right endpoint without browsing the reference docs.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

Cloud Billing API

→

Manages billing accounts and project-account links that budgets attach to.

Use Cloud Billing to set up the billing account; use Budgets to add spend alerts on top.

Complementary

BigQuery Reservation API

→

Controls BigQuery slot capacity that drives a major chunk of GCP spend.

Use Reservation to control BigQuery cost shape; use Budgets to alert when spend regardless of source crosses a cap.

Complementary

Cloud Resource Manager API

→

Lists and manages projects that budgets filter on.

Use Resource Manager to discover the project IDs to scope a budget to.

FAQs

Specific to using Cloud Billing Budget API through Jentic.

What authentication does the Cloud Billing Budget API use?

The API uses Google OAuth 2.0 with the cloud-billing or cloud-platform scope. Through Jentic the OAuth refresh token sits in the encrypted vault and the agent only receives short-lived access tokens scoped to the budget operations.

Can I create a budget that covers only a specific project?

Yes. POST /v1/{parent}/budgets with budgetFilter.projects set to projects/PROJECT_ID limits the budget to spend in that project. You can also filter by services, labels, calendarPeriod, and creditTypesTreatment.

What are the rate limits for the Cloud Billing Budget API?

Quotas are billing-account-level: typically a few thousand budgets per billing account and modest write QPS on the same budget. Read QPS is bursty up to several hundred per second per account. Specific values are visible in the Google Cloud quotas console.

How do I wire budget alerts to Pub/Sub through Jentic?

Search Jentic for 'add a Pub/Sub notification to a budget', load the schema for PATCH /v1/{name}, and execute with notificationsRule.pubsubTopic set to projects/PROJECT/topics/TOPIC and an updateMask of notificationsRule. Jentic forwards the OAuth token automatically.

Does a budget stop spending when it hits 100 percent?

No. Budgets only emit notifications at the configured thresholds. They do not block resource provisioning or stop existing workloads. Combine them with Cloud Functions or Workflows triggered from the Pub/Sub topic to enforce automated responses.

Can I limit what my agent is allowed to do with the Cloud Billing Budget API?

Yes. Because you run Jentic One yourself, your own rules decide which operations and credentials the agent may use, and this API puts the billing account and budget in the URL path (/v1/{+parent}/budgets and /v1/{+name}), so a rule can pin the agent to a single billing account's budgets and nowhere else. You choose the exact operations it may call, so you can let it create budgets and read their threshold rules while leaving delete out unless you explicitly add it. The stored Google OAuth credentials are injected only at execution time, and the agent receives short-lived scoped access tokens rather than the refresh token.

GET STARTED

Start building with Cloud Billing Budget API

Explore with Jentic One
View OpenAPI Document