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.
18 endpointsThe 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.
5 endpointsStep 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 | shStep 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 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.