Orchestration Runs

Account status — using account 2

• Window usage so far: 7,254,237 tokens ($6.93) — 38% of its own last observed ceiling
• Total dispatches on this account: 54

Account status — using account 2

• Window usage so far: 7,292,595 tokens ($7.07) — 38% of its own last observed ceiling
• Total dispatches on this account: 55

Phase Timeline¶

SHARED TOTAL: 49s, 76,581 tokens, $0.2451, 3 row(s) with no token data (rows 1–5)

Total Run Time: 2m (wall clock, 18-09-2026 19:31:26 → 18-09-2026 19:33:02 IST — not a sum of the per-side totals above, since sides overlap)
Total Tokens Consumed: 76,581 (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 5,090 · output 1,124 · cache-create 33,332 · cache-read 37,035 (48% 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.2451 (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: 7,330,818 tokens ($7.17) — 38% of its own last observed ceiling
• Total dispatches on this account: 56

Account status — using account 2

• Window usage so far: 7,527,395 tokens ($7.50) — 39% of its own last observed ceiling
• Total dispatches on this account: 57

Account status — using account 2

• Window usage so far: 7,566,097 tokens ($7.54) — 40% of its own last observed ceiling
• Total dispatches on this account: 58