Cargo Billing

Cargo CLI — Billing

Billing and credit management: pulling usage metrics, checking subscription status, viewing invoices, and managing credits.

> See references/response-shapes.md for full JSON response structures. > See references/troubleshooting.md for common errors and how to fix them. > See references/examples/usage-metrics.md for usage metric and subscription examples.

Prerequisites

See [../cargo/references/prerequisites.md](../cargo/references/prerequisites.md) for install, login (--oauth / --token), JSON output conventions, and error shapes. Verify the session with cargo-ai whoami before running any of the commands below.

Admin-only: every command in this skill requires a token with admin access on the workspace. Non-admin tokens return {"errorMessage":"forbidden"}.

Discover resources first

Usage metrics can be filtered and grouped by resource UUID. Discover them before querying.

cargo-ai orchestration play list            # all plays (name, workflowUuid)
cargo-ai orchestration tool list            # all tools (name, workflowUuid)
cargo-ai ai agent list                     # all agents (uuid, name)
cargo-ai connection connector list          # all connectors (uuid, name, integrationSlug)
cargo-ai storage model list                # all models (uuid, name, slug)

Quick reference

cargo-ai billing usage get-metrics --from  --to 
cargo-ai billing usage get-metrics --from  --to  --group-by workflow_uuid
cargo-ai billing subscription get
cargo-ai billing subscription get-invoices
cargo-ai billing subscription create-portal-session

Estimating cost before running a batch

Before triggering a large batch, estimate credit consumption to avoid unexpected charges.

Step 1 — Check current credit balance:

cargo-ai billing subscription get
# → subscriptionAvailableCreditsCount - subscriptionCreditsUsedCount = remaining credits

Step 2 — Estimate cost from a sample run:

Run the workflow on a single record first and measure credits consumed:

# Run on one record
cargo-ai orchestration run create --workflow-uuid  --data '{...}'
# → poll to completion

# Check credits used for that run
cargo-ai billing usage get-metrics \
  --from  --to  \
  --workflow-uuid 
# → .totalUsage = credits consumed today for this workflow

Step 3 — Project batch cost:

estimated_cost = credits_per_record × number_of_records

Compare against subscriptionAvailableCreditsCount - subscriptionCreditsUsedCount before proceeding.

Step 4 — Monitor during the batch:

# Check running costs mid-batch
cargo-ai billing usage get-metrics \
  --from  --to  \
  --workflow-uuid 

Cost levers:

| Action | Effect | |---|---| | Use a cheaper model (e.g. gpt-4o-mini vs gpt-4o) | Significant reduction for AI nodes | | Add filter nodes early in the graph | Skip ineligible records before expensive connector calls | | Set fallbackOnFailure: false | Stop the run early on failures instead of continuing to downstream nodes | | Reduce maxSteps on agent nodes | Limit how many tool calls an agent can make per record |

> To find out which node or provider dominates a play's spend before picking a lever, follow the attribution runbook in [../cargo-diagnostics/references/play-optimize-credits.md](../cargo-diagnostics/references/play-optimize-credits.md).

Usage metrics

Pull credit and usage data for any time range, optionally filtered and grouped.

# Basic usage for a period
cargo-ai billing usage get-metrics --from  --to 

# Group by dimension
cargo-ai billing usage get-metrics --from  --to  --group-by workflow_uuid
cargo-ai billing usage get-metrics --from  --to  --group-by connector_uuid
cargo-ai billing usage get-metrics --from  --to  --group-by integration_slug
cargo-ai billing usage get-metrics --from  --to  --group-by model_uuid
cargo-ai billing usage get-metrics --from  --to  --group-by agent_uuid

# Filter by specific resource
cargo-ai billing usage get-metrics --from  --to  --workflow-uuid 
cargo-ai billing usage get-metrics --from  --to  --agent-uuid 
cargo-ai billing usage get-metrics --from  --to  --connector-uuid 
cargo-ai billing usage get-metrics --from  --to  --integration-slug 

# Specify unit
cargo-ai billing usage get-metrics --from  --to  --unit credits

--group-by values: workflow_uuid, connector_uuid, model_uuid, integration_slug, agent_uuid.

Available filters: --workflow-uuid, --model-uuid, --connector-uuid, --integration-slug, --slug, --agent-uuid. Combine with --group-by and --unit.

Subscription and credits

cargo-ai billing subscription get                    # current plan, credits used/available, period dates
cargo-ai billing subscription get-invoices            # invoice history (amounts in cents)
cargo-ai billing subscription get-credit-card         # card on file
cargo-ai billing subscription create-portal-session   # Stripe portal URL for self-service billing

Remaining credits = subscriptionAvailableCreditsCount - subscriptionCreditsUsedCount from subscription get.

Note: Invoice amounts are returned in cents. Divide by 100 for the dollar value.

Help

Every command supports --help:

cargo-ai billing usage get-metrics --help
cargo-ai billing subscription get --help
cargo-ai billing subscription get-invoices --help

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

• Author: getcargohq
• Source: getcargohq/cargo-skills
• License: MIT
• Homepage: https://getcargo.ai

Install and usage instructions live in the source repository linked above.