LocalCloud Service Usage Local Emulator
Get started
local.cloud — Service Usage Local Emulator .md Open tab
LocalCloud Google Cloud in-a-box

Service Usage

Service Usage manages which Google APIs and services are enabled for a project. LocalCloud supplies the documented preflight responses used by provisioning clients.

When to use Service Usage

Typical uses

Use when provisioning clients check API availability or request service enablement before creating resources. Local preflight responses let you exercise those client flows.

Examples

  • API enablement preflight checks
  • Provisioning-client compatibility 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 SERVICE_USAGE_EMULATOR_HOST
eval "$(localcloud env)"

Test an API enablement preflight

  1. Request enablement for a service through the local facade.
  2. Poll the returned operation.
  3. Verify the response without treating it as runtime service activation.

Documented workflows

  • Service list/get/enable/batchEnable preflights and completed operation polling

Service boundaries

  • Reports ENABLED; runtime activation uses LocalCloud service controls
  • No quota enforcement, billing, or project-specific entitlement
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.

Integration

Build an integration test loop

Start the runtime, verify readiness, exercise your SDK, and clean up test state.

Open guide
Agent testing

Use Service Usage with an AI agent

Before the agent changes application logic, have it create local Service Usage 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