Orchestration Runs

Account status — using account 2

• Window usage so far: 4,283,381 tokens ($4.44) — 22% of its own last observed ceiling
• Total dispatches on this account: 49

Account status — using account 2

• Window usage so far: 4,321,266 tokens ($4.57) — 23% of its own last observed ceiling
• Total dispatches on this account: 50

Phase Timeline¶

ORCHESTRATOR TOTAL: 34s, 0 tokens, $0.0000 (rows 8–9)
SHARED TOTAL: 2m, 400,417 tokens, $1.0905, 3 row(s) with no token data (rows 1–7)

Total Run Time: 3m (wall clock, 18-09-2026 18:38:17 → 18-09-2026 18:40:54 IST — not a sum of the per-side totals above, since sides overlap)
Total Tokens Consumed: 400,417 (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,191 · output 5,493 · cache-create 150,570 · cache-read 234,163 (58% 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.0905 (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: 4,359,498 tokens ($4.68) — 23% of its own last observed ceiling
• Total dispatches on this account: 51

Account status — using account 2

• Window usage so far: 4,651,795 tokens ($5.34) — 24% of its own last observed ceiling
• Total dispatches on this account: 52