Orchestration Runs

Account status — using account 2

• Window usage so far: 8,851,903 tokens ($9.94) — 46% of its own last observed ceiling
• Total dispatches on this account: 69

Account status — using account 2

• Window usage so far: 8,891,670 tokens ($10.09) — 46% of its own last observed ceiling
• Total dispatches on this account: 70

Phase Timeline¶

ORCHESTRATOR TOTAL: 0s, 0 tokens, $0.0000 (rows 8)
SHARED TOTAL: 1m, 155,080 tokens, $0.4741, 3 row(s) with no token data (rows 1–7)

Total Run Time: 1m (wall clock, 21-09-2026 12:31:33 → 21-09-2026 12:32:35 IST — not a sum of the per-side totals above, since sides overlap)
Total Tokens Consumed: 155,080 (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,252 · output 2,689 · cache-create 62,373 · cache-read 79,766 (51% 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: $0.4741 (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: 8,930,017 tokens ($10.20) — 47% of its own last observed ceiling
• Total dispatches on this account: 71

Account status — using account 2

• Window usage so far: 8,968,889 tokens ($10.31) — 47% of its own last observed ceiling
• Total dispatches on this account: 72