Browse documentation

Billing and administration

Usage, limits, and metering

Monitor workflow executions, messages, AI cost, API usage, number limits, storage, and unsettled usage.

AdministratorsAutomation buildersDevelopersBeginnerAvailable

What this guide covers

  • Usage views and discovery endpoints show consumption and current entitlements; Analytics adds workflow-level execution and cost context.
  • Prerequisites: Know whether you are reviewing account, Agent Project, or Developer Platform scope.
  • Result: The record scope, state, amount, and relevant operation ID explain the observed consumption.
  • Limit: The audited UI does not expose a universal overage switch or cross-service CSV export.

What this is and when to use it

Usage views and discovery endpoints show consumption and current entitlements; Analytics adds workflow-level execution and cost context.

When to use Usage, limits, and metering
Use it whenExpected outcome
You need to plan volume.The record scope, state, amount, and relevant operation ID explain the observed consumption.
An operation is blocked by a limit.The record scope, state, amount, and relevant operation ID explain the observed consumption.
Billing appears different from an estimate.The record scope, state, amount, and relevant operation ID explain the observed consumption.

Before you begin

  1. Know whether you are reviewing account, Agent Project, or Developer Platform scope.

Complete the task

  1. Review account Billing and transactions.
  2. Review Agent Analytics and Billing for workflow execution cost.
  3. Review API Usage for Developer Platform records.
  4. Treat reserved or needs_reconciliation usage as unsettled.
  5. Use the current subscription/limit source instead of hard-coding a seed tier.

Confirm it worked

  1. The record scope, state, amount, and relevant operation ID explain the observed consumption.

Common problems

Usage, limits, and metering troubleshooting
SymptomWhat to check
A limit was reachedReduce usage, remove unused resources, or select an available plan upgrade.
Usage seems duplicatedCorrelate public message/execution and idempotency identifiers before retrying.

Current limitations

The audited UI does not expose a universal overage switch or cross-service CSV export.

Where to go next