Zeta · Assistants
Every tool's ceiling, how close you are to it, and which team assistant is spending the AI budget.
Every assistant is Zeta at work — one AI, under your rules
AI spend this month
$0.00
every request in this period was priced
Budget
none set
without a cap, spend is unbounded
Near a ceiling
0
nothing above 80% of its limit
Calls stopped by a limit
0
no ceiling has fired
| Tool | Class | Busiest team assistant, last hour | Organisation, last day | Refused | State |
|---|---|---|---|---|---|
| model.complete | reads | 0 / 120 | 0 / 5000 | none | unused |
| knowledge.search | reads | 0 / 120 | 0 / 5000 | none | unused |
| crm.read | reads | 0 / 120 | 0 / 5000 | none | unused |
| crm.write | writes | 0 / 30 | 0 / 500 | none | unused |
| tasks.write | writes | 0 / 30 | 0 / 500 | none | unused |
| reports.read | reads | 0 / 120 | 0 / 5000 | none | unused |
| systems.read | reads | 0 / 120 | 0 / 5000 | none | unused |
| alerts.write | writes | 0 / 30 | 0 / 500 | none | unused |
| revenue.opportunities.read | reads | 0 / 120 | 0 / 5000 | none | unused |
| revenue.quality.read | reads | 0 / 120 | 0 / 5000 | none | unused |
| revenue.attribution.read | reads | 0 / 120 | 0 / 5000 | none | unused |
| revenue.campaigns.read | reads | 0 / 120 | 0 / 5000 | none | unused |
| revenue.campaigns.write | writes | 0 / 30 | 0 / 500 | none | unused |
| dial.queues.read | reads | 0 / 120 | 0 / 5000 | none | unused |
| medical.cohort | patient data | 0 / 30 | 0 / 400 | none | unused |
| medical.recall | patient data, writes | 0 / 4 | 0 / 20 | none | unused |
Windows are rolling, not calendar buckets, so capacity returns gradually rather than all at once at midnight. A run bounded at six steps is not a ceiling: a team assistant on a five-minute schedule stays inside the step limit and still makes over a thousand calls a day. These limits are enforced where the scope check is, so a workflow or a scheduled job cannot route around them.
Reads
120/worker/hour · 5000/org/day
A read that runs too often wastes money and nothing else.
Writes
30/worker/hour · 500/org/day
A write that runs too often creates rows somebody has to clean up.
Patient reads
30/worker/hour · 400/org/day
Population counts only, but every call is a PHI access somebody may have to account for.
Patient writes
4/worker/hour · 20/org/day
This contacts real patients. Nothing undoes an unwanted call, so the ceiling is low enough that a runaway is caught the same day.
2 of the catalog’s tools reach patient data. Their class comes from the catalog entry itself, not from the name — so a new Medical tool cannot pick up an ordinary ceiling because one field was missed.
No team assistants deployed.
Spend is attributed per team assistant from the moment one runs, with no configuration.
A request whose cost the provider did not report is counted separately rather than added as zero. A total that quietly omits what it could not price looks authoritative and is not, and somebody eventually builds an invoice on it. A team assistant running locally costs nothing and says so — that is a configuration fact, not a saving.