Orchestration Runs

Account status — using account 2

• Window usage so far: 2,227,344 tokens ($3.65) — 13% of its own last observed ceiling
• Total dispatches on this account: 94

Account status — using account 2

• Window usage so far: 3,005,698 tokens ($4.62) — 18% of its own last observed ceiling
• Total dispatches on this account: 95

Phase Timeline¶

ORCHESTRATOR TOTAL: 3m, 0 tokens, $0.0000 (rows 8–11)
SHARED TOTAL: 5m, 984,895 tokens, $1.6352, 4 row(s) with no token data (rows 1–12)

Total Run Time: 8m (wall clock, 14-09-2026 16:04:57 → 14-09-2026 16:13:04 IST — not a sum of the per-side totals above, since sides overlap)
Total Tokens Consumed: 984,895 (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 10,334 · output 19,551 · cache-create 178,131 · cache-read 776,879 (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.6352 (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: 3,074,105 tokens ($4.83) — 18% of its own last observed ceiling
• Total dispatches on this account: 96

Account status — using account 2

• Window usage so far: 3,112,102 tokens ($4.94) — 18% of its own last observed ceiling
• Total dispatches on this account: 97

Account status — using account 2

• Window usage so far: 18,851,262 tokens ($14.03) — unknown (no real usage-limit rejection observed yet for this account) of its own last observed ceiling
• Total dispatches on this account: 34