Usage & Billing

Billing for an embedded fleet follows one rule: credit is pooled, usage is attributed. Your org pays from one balance; every workspace reports its own share of the spend, so you always know what the feature costs to run per customer.

One pool

Plan, allowance, and prepaid balance live on the org's primary workspace and cover the whole org. A customer workspace never needs its own top-up, and there's no per-workspace balance to babysit — a run in any workspace draws from the shared pool. Manage the plan and top-ups from the primary workspace's Settings → Billing, like any other workspace; see Plans & Billing for how credits work.

When the pool runs out, runs are gated across the org until it's topped up. Suspending a workspace is never about billing — it's your lifecycle switch for offboarded customers.

Per-customer attribution

GET /api/v1/org/usage returns the pooled balance and month-to-date spend, broken down by workspace:

{
  "tier": "enterprise",
  "balance_usd_micros": 412500000,
  "current_month_spend_usd_micros": 87500000,
  "workspaces": [
    {
      "id": "…",
      "name": "Acme Tools",
      "headless": true,
      "lifecycle": "active",
      "current_month_spend_usd_micros": 61250000
    }
  ]
}

Amounts are in millionths of a USD (61250000 = $61.25). This is the number to feed your own pricing: meter it, margin it, or bundle it — the per-customer cost is yours to see either way.

For finer grain — per agent, per run, per day — the Analytics endpoints work per workspace like everything else: send X-Workspace-Id with an org key and you get that customer's breakdown.