Agent fleet
Six agents, one operating picture
polling every 5 s · click any agent for its run history
Agents online
6 / 6
1 degraded · 0 offline
Actions today
1,284
+11.2% vs 7-day avg
Awaiting approval
9
oldest waiting 21 m
Autonomy rate
92.4%
97 of 1,284 escalated
Median approval
6m 40s
−1m 12s week on week
Spend today
₪118
to 13:42 · run-rate ₪141
Execution timeline
last 3 hours · 10:42 → 13:42 IDT
completed run
retried
failed
held for approval
Action queue
Nothing irreversible runs without a human
9 pending · 0 decided this session
Approval SLA
30 min
Unactioned requests expire and are returned to the agent as "declined by timeout".
Auto-approved today
1,187
Actions that fell inside the standing policy ceilings — logged, never queued.
Rejection rate
4.1%
Every rejection is fed back as a correction on the agent's next planning pass.
Event stream
Every action an agent takes, in order
retained 90 days · exportable to your SIEM
Cost & usage
What the fleet costs, per agent, per day
billing period 06 Jul – 05 Aug 2026 · day 28 of 31
Period budget
₪3,884 of ₪4,500 consumed
86.3% consumed
₪138.7 average day
projected close ₪4,302 · 95.6% of budget
alert threshold 90% → notify ops lead
Daily spend by agent
last 14 days · ₪ · click a legend key to isolate
| Agent▲ | Runs▲ | Tokens in▲ | Tokens out▲ | Avg ₪/run▲ | Fail rate▲ | Period spend▲ | Share▲ |
|---|---|---|---|---|---|---|---|
| Fleet total | 18,710 | 122.0 M | 19.5 M | 0.21 | 1.4% | ₪3,884 | 100.0% |
Cache hit rate
61.8%
Prompt caching on the two orchestration agents saves an estimated ₪612 per period.
Cost per resolved case
₪0.94
Down from ₪1.61 at go-live, on 4,128 cases resolved this period.
Model mix
3 tiers
Routing sends 71% of calls to the small tier; only planning steps use the large one.
Guardrails
The rules that decide what needs you
policy version 14 · changed 29 Jul 2026
Global autonomy
The single switch. Turning it off lets every agent finish its current step and then hold — queued actions keep collecting, nothing new executes. Used during incidents and month-end close.
| Action class | Scope | Auto-run ceiling | Approver | Timeout | Reversible |
|---|---|---|---|---|---|
| payment.release | Ledger | ₪0 — always queued | Finance lead | 30 m | no |
| customer.email.send | Relay | ₪500 goodwill value | Duty manager | 30 m | no |
| shipment.reroute | Atlas | ≤ 10 shipments | Duty manager | 15 m | yes |
| schema.migrate | Forge | staging only | Platform owner | 60 m | no |
| worker.restart | Sentry, Forge | 2 per hour | On-call | 10 m | yes |
| doc.publish.internal | Quill | unlimited | — auto | — | yes |
| invoice.match | Ledger | confidence ≥ 0.93 | — auto | — | yes |
| exception.escalate | Atlas, Relay | ≤ 20 per batch | — auto | — | yes |
Escalation chain
what happens when nobody answers
STEP 01
Queued
The action lands here with its payload, cost estimate and a plain-language reason it needs a human.
STEP 02
Nudge at 10 min
A WhatsApp ping goes to the named approver with an approve / reject link — no dashboard login needed.
STEP 03
Escalate at 20 min
The request moves to the backup approver and is marked amber on this board.
STEP 04
Expire at 30 min
Returned to the agent as declined-by-timeout. The agent re-plans instead of retrying blindly.