Watch every dollar your agent fleet burns.
Your coding agents run up a bill you only see three weeks later on the invoice. OmnisVigil turns your OmnisRouter receipts into an honest ledger: cost per commit, per repo, per team, live. It catches the looping agent quietly burning $1,382 an hour and stops it before the invoice does, and it proves with an open benchmark which work never needed a frontier model. Team-level, and never a per-developer scoreboard.
Illustrative view. The $1,382-in-one-hour looping agent is a real, publicly reported incident.
Agentic coding detached the cost from the sticker
A $20 seat anchors what you expect to pay. Then an agent reloads the whole codebase every turn, runs unattended, loops on a bad tool call, and the meter runs the entire time. Uber burned its 2026 AI budget in four months. One team was charged $1,382 in a single hour when an agent looped tagging a backlog. The pain in the wild is always the same two words: bill shock. And it lands after the money is gone, because the tools show you one aggregate number and no daily cap.
It's unpredictable
Some days $40, some days under $10, then a single session that dwarfs the month. You can't forecast it and you can't explain it after the fact.
It loops and burns
Agents retry, explore dead ends, and re-bill the full context every turn. Fifty thousand tokens to do five thousand tokens of work, and nothing stops it.
You can't see inside it
Total tokens, total cost, maybe per model. Never per commit, per repo, per team, or per agent run. So nobody can say what anything cost.
Every dollar, attributed to the work that spent it
OmnisVigil reads the receipt OmnisRouter already writes for every request and rolls it up into the numbers a team lead needs: cost per commit, per repo, per team, per agent session. No prompt content, no code, no per-developer league table. Only the money: where it went, and whether it was worth it, in a view you can hand to finance without flinching.
# the receipt OmnisRouter writes, rolled up by OmnisVigil commit a1f9c2e payments-api 3 requests $0.31 routed gpt-5-nano refactor tests $0.004 saved vs frontier -$0.12 routed gemini-flash summarise diff $0.001 saved vs frontier -$0.03 escalated opus-5 design the migration $0.30 needed the frontier # and the alert that matters, in real time 14:03 RUNAWAY payments-api agent 1.3B tokens/hr $1,382 cap hit → paused
The escalation line is the honesty. When a change genuinely needed the frontier model, the ledger says so. When it didn't, you see exactly what the cheaper model did and what it saved. Nobody's hiding the number to protect a margin.
Hard caps, live alerts, and a cut-off
Optimising the average call is not enough when one runaway session can cost more than a month. OmnisVigil watches spend as it happens and gives you the controls the seat-based tools gate behind enterprise: hard caps per team, per agent and per task, an anomaly alert the moment a session goes vertical, and a cut-off that stops the loop before it stops your budget.
Hard caps
Set a daily or monthly ceiling per team, repo, agent or task. A spike trips it mid-day and pauses the offender, so you find out in minutes, not on the invoice.
Runaway detection
A looping or retrying agent shows up as a session going vertical against its own history. OmnisVigil flags it live and can pause it automatically.
One cut-off
Stop a single agent session on the spot and keep its log. The work you meant to run keeps running. The loop that was burning money does not.
The only cost layer whose incentive is to shrink your bill
Look at how the tools around this problem make money. OpenRouter passes provider pricing through but charges a fee on the credits you buy, around 5%. Requesty adds a flat 5% markup. Both earn more as your bill grows, so "we save you money" runs against their own revenue. Observability tools like Langfuse and Helicone log what you spent and stop there. OmnisVigil charges a flat fee, runs on your own keys, and takes nothing off the top. It doesn't ask you to trust a savings claim either: it points at the open OmnisBench benchmark that measures which model each kind of work needs, so "cheaper" is a number you can reproduce.
vs marketplaces
OpenRouter, Requesty. Genuinely useful for one bill across many models, and you can keep using them. But they take a percentage of spend, so shrinking your bill works against them. OmnisVigil sits alongside and does the part they won't.
vs observability
Langfuse, Helicone. Strong at logging and tracing what you spent. They don't act on it: no cheapest-capable routing, no hard cap, no cut-off. OmnisVigil closes the loop from measured spend to cheaper-model action.
vs quality routers
Not Diamond, Martian. They claim big savings on their own benchmarks. The independent RouterArena ranks Not Diamond near the bottom of commercial routers, for frequently choosing expensive models. OmnisVigil's savings ride on the open, reproducible OmnisBench instead.
Credit where it's due: each of these is good at what it was built for, and OmnisVigil sits next to them, not on top of them. The difference is the one thing a spend-percentage business can't offer, an incentive to make the number go down.
It sits on receipts you already have
Point your agents at OmnisRouter, and every request comes back with a receipt: the model, the cost, and what a cheaper-capable model would have cost. OmnisVigil is the layer that reads those receipts and turns them into a fleet view, with the caps and alerts on top.
Content-free by construction
OmnisVigil sees costs, models and metadata, never prompts, code or keys. The receipt is designed to carry the money, not the work.
Attributed to the work
Commit, repo, team and agent session come from the request context, so spend rolls up the way an engineering org is shaped.
Self-host or hosted
Run the whole thing yourself next to OmnisRouter, or use the hosted dashboard for the team view. Your traffic and keys stay yours either way.
Team-level, never a per-developer scoreboard
OmnisVigil reports spend by team, repo and workload, so a lead can govern a budget and defend it upward. It will not rank individual engineers by tokens or cost. Surveillance dressed as FinOps is a different product, and not one we'll build. This is a line, not a setting.
One flat fee, never a cut of your spend
Every plan is the whole product: cost attributed to the work, the savings ledger, the kill-switch and hard spend caps. Plans change on four things only, how many people are in, how far the history goes back, whether you need enterprise SSO, and whether you need an audit log. We win when you cut your bill, not when you keep spending, so we never take a slice of it.
For one. The whole app, one seat, so you can see your own spend before anyone signs a cheque.
- ✓ 1 member, just you
- ✓ 1 month of history
- ✕ Enterprise SSO and directory sync
- ✕ Audit log
The moment you add a teammate. Unlimited members on one flat fee, not a price per head.
- ✓ Unlimited members
- ✓ 3 months of history
- ✕ Enterprise SSO and directory sync
- ✕ Audit log
When finance and security want in. SSO, directory sync and a full audit trail.
- ✓ Unlimited members
- ✓ 13 months of history
- ✓ Enterprise SSO and directory sync
- ✓ Audit log
Unlimited history and terms that fit how you buy. Talk to us and we'll shape it round you.
- ✓ Unlimited members
- ✓ Unlimited history
- ✓ Enterprise SSO and directory sync
- ✓ Audit log
Every plan starts the same way: sign in, and a new identity sets up your workspace on Free. Add a teammate and you're on Team. Move up to Business or Enterprise when you need SSO, an audit log or a longer window of history. Enterprise SSO (Okta, Entra, Google Workspace) and SCIM directory sync arrive at Business and above.
See it on your own bill
OmnisVigil is in early access, and you can start on your own for nothing. Sign in, and that sets up your workspace on Free. There's no separate sign-up form: it's a magic link to your email, or Google, GitHub and the rest. Then run OmnisRouter in collect mode on a machine using your Claude subscription. It reads your usage read-only, reprices it, and shows what routing would have saved and where the runaways were. The first number you see is your own. If it isn't real, we'll tell you.
Frequently asked
Straight answers to what teams ask about agent-fleet cost.
What is OmnisVigil, in one line?
Does it see our code or prompts?
Is this a per-developer productivity tracker?
How is it different from an LLM observability tool?
Why should we trust the savings number?
Do we have to self-host?
How do we sign in, and what about SSO?
Is this priced per seat?
Where it stands
Early access, on purpose
OmnisVigil is being built in the open with a handful of teams. The fastest way in is to let us reprice a month of your usage, so the first number you see is your own.
It needs the receipts
The ledger is only as good as the request context. Run your agents through OmnisRouter and every call carries the cost, the model and the cheaper-capable delta that OmnisVigil rolls up.
Savings are measured, then modelled
Coding and math savings come from real OmnisBench runs. Where we estimate, we label it an estimate. We would rather show you a smaller honest number than a big unprovable one.
Dashed prices, dated
Every cost figure comes from a committed, dated pricing snapshot, shared with OmnisRouter and OmnisBench, so a receipt reproduces even after list prices move.