Orchestration Runs

Account status — using account 2

• Window usage so far: 3,211,978 tokens ($5.28) — 19% of its own last observed ceiling
• Total dispatches on this account: 99

Account status — using account 2

• Window usage so far: 3,895,219 tokens ($6.07) — 23% of its own last observed ceiling
• Total dispatches on this account: 100

Phase Timeline¶

ORCHESTRATOR TOTAL: 4m, 0 tokens, $0.0000 (rows 8–11)
SHARED TOTAL: 5m, 1,156,063 tokens, $1.9185, 3 row(s) with no token data (rows 1–10)

Total Run Time: 9m (wall clock, 14-09-2026 16:38:11 → 14-09-2026 16:47:35 IST — not a sum of the per-side totals above, since sides overlap)
Total Tokens Consumed: 1,156,063 (plus 3 row(s) whose usage was never captured — run execution_tracker.py enrich-audit to backfill. This is a floor, not the total.)
Token breakdown: input 10,346 · output 20,820 · cache-create 215,618 · cache-read 909,279 (79% of the total). Cache-read is context a node re-sends to itself across its own tool-use turns, billed at roughly a tenth of fresh input — a large Tokens number that is mostly cache-read is a long tool loop, not a large workload.
Total Cost: $1.9185 (plus 3 row(s) whose usage was never captured — run execution_tracker.py enrich-audit to backfill. This is a floor, not the total.)

Account status — using account 2

• Window usage so far: 3,963,340 tokens ($6.28) — 23% of its own last observed ceiling
• Total dispatches on this account: 101

Account status — using account 2

• Window usage so far: 4,001,304 tokens ($6.38) — 24% of its own last observed ceiling
• Total dispatches on this account: 102

Account status — using account 2

• Window usage so far: 19,038,522 tokens ($14.74) — unknown (no real usage-limit rejection observed yet for this account) of its own last observed ceiling
• Total dispatches on this account: 36