LocalCloud Cloud Billing Local Emulator
Get started
local.cloud — Cloud Billing Local Emulator .md Open tab

Cloud Billing

Cloud Billing connects projects to billing accounts on Google Cloud. LocalCloud exposes selected account and project billing metadata for provisioning tests.

When to use Cloud Billing

Typical uses

Use when provisioning automation needs to discover a billing account or verify a project's billing association. Local tests exercise the metadata flow with test-owned resources.

Examples

  • Billing-account lookup flows
  • Project billing-link metadata tests
Operations

Explore another service

View all
Local workflow

Example usage

Install the CLI, start LocalCloud, and export its environment in the same shell. Generated endpoints account for remapped ports.

1. Install and start · shell
curl -fsSL https://local.cloud/install.sh | sh
localcloud start --local-only
# Export GOOGLE_CLOUD_PROJECT and CLOUD_BILLING_EMULATOR_HOST
eval "$(localcloud env)"

Check a project’s billing metadata

  1. Create the documented local billing metadata.
  2. Read or update the project billing association.
  3. Verify the returned account and billing-enabled fields.

Documented workflows

  • Billing-account and budget metadata CRUD; selected Terraform paths

Service boundaries

  • No cost accumulation or threshold notifications
  • No billing exports or budget-triggered automation
Try it in your project

Code examples and integrations

Start with the local guides. Official Google Cloud samples may need endpoint changes and can cover features outside the workflows listed here.

Agent testing

Use Cloud Billing with an AI agent

Before the agent changes application logic, have it create local Cloud Billing state, read it back with the project SDK, and note which feature the check covered. That first local call catches accidental production routing and needs no GCP account, service-account key, or billing project.

Configure this repo

Set up this repository to use LocalCloud for local GCP development. First read https://local.cloud/ai/agents.md, then inspect this repo, identify the GCP services and SDK language, configure emulator environment variables, and run the narrowest integration test against localhost. Do not use real GCP credentials or production endpoints.

Production endpoints, auth, IAM, quotas, regional behavior, and final release validation still need the target Google Cloud project.

Agent resources has more prompts and the AGENTS.md template.

Related guides

Desktop view