Orchestration Runs

Account status — using account 2

• Window usage so far: 60,373 tokens ($0.21) — 1% of its own last observed ceiling
• Total dispatches on this account: 112

Phase Timeline¶

ORCHESTRATOR TOTAL: 12m, 0 tokens, $0.0000 (rows 8–12)
SHARED TOTAL: 6m, 844,690 tokens, $2.0555, 4 row(s) with no token data (rows 1–11)

Total Run Time: 18m (wall clock, 15-09-2026 12:36:13 → 15-09-2026 12:54:27 IST — not a sum of the per-side totals above, since sides overlap)
Total Tokens Consumed: 844,690 (plus 4 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 7,792 · output 33,275 · cache-create 225,168 · cache-read 578,455 (68% 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: $2.0555 (plus 4 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: 247,914 tokens ($0.95) — 3% of its own last observed ceiling
• Total dispatches on this account: 113

Account status — using account 2

• Window usage so far: 303,922 tokens ($1.30) — 4% of its own last observed ceiling
• Total dispatches on this account: 114

Account status — using account 2

• Window usage so far: 361,966 tokens ($1.41) — 5% of its own last observed ceiling
• Total dispatches on this account: 115