The problem with sharing one key
Give a team one shared key and you cannot tell who spent what, and one runaway job eats everyone’s allowance. Split it into per-agent budgets and the picture changes immediately.
Per-agent and per-tenant
- Each agent has its own tool allowlist and budget.
- Tenants keep one project’s activity separate from another’s.
- Approval rules gate the sensitive actions.
- The audit trail shows who triggered what.
Approvals where they matter
You do not need approval for reading a file. You might for deleting one or spending beyond a threshold. The rule is set once, and the agent holds the action until a human says yes.
Onboarding a teammate
- Add them to the workspace.
- Give their device a token (not a key).
- Assign them agents or let them create their own.
- Revoke in one click when they leave.
What the bill looks like
Spend is visible per agent, per day, and per provider. When someone asks "why is this month high?", the answer is a query, not an investigation.