A dev kicks off an agent and walks into a meeting. Forty minutes later: $180 gone, stuck in a retry loop — and nothing native to your providers could stop it mid-run. Oolyx sits in the request path and revokes a runaway agent's ability to spend, before the bill compounds.
Agent mode gives models autonomy: run commands, edit files, call tools, spawn sub-agents, iterate on failures. When it works, it's the most productive interface your engineers have. When it doesn't, the failure compounds — each retry resends the whole accumulated context, sub-agents fan out into parallel spenders, and unattended sessions keep burning long after everyone stopped watching.
4:00 PM — "Refactor the auth module, make the tests pass." The dev heads to standup. 4:07 — a failing assertion; the agent retries with its full history attached. 4:19 — retry number eight is sending 200K+ tokens per call, mostly its own failed attempts. 4:41 — the dev is back: stack traces, no working code, and roughly $180 in tokens that finance will discover at month-end.
The scenario is hypothetical. The pattern isn't: VentureBeat found that one in five enterprises can't stop a runaway AI agent's spending in real time.
Every provider gives you something — and none of it intervenes mid-run.
Oolyx deploys as a proxy in the request path between your AI tools and the model providers. Every call passes through it — so enforcement is real-time, and scoped to exactly the entity that's misbehaving.
Session spend is evaluated between rounds of an agent run. Cross the quota and the next API call is blocked before it leaves your network — the loop dies at call 12, not call 400.
Per-entity API keys attribute every cent to a person, agent, or application — so quotas and kills hit one runaway entity while the rest of the org never notices.
Every enforcement action leaves a full audit trail: which entity was stopped, what each round cost, and which rule fired. Interventions become five-minute reviews, not arguments.
Legitimate heavy job caught by a limit? Admins approve a scoped, temporary extension in seconds — the work continues, the guardrail stays.
A kill switch only works if you'll actually deploy it in the hot path. Oolyx is engineered so that decision is easy.