For Finance and FinOps

Know what AI costs before the invoice does.

Every AI call is priced within minutes, at the price in force when it was made, and owned by a team, an application, an agent and a person. Budgets act before the invoice does, and Finance runs all of it without admin rights.

Vidai Control room · Dashboard
The FinOps dashboard: spend, price per call, routing savings and budgets, each currency on its own.
The FinOps dashboard: spend, price per call, routing savings and budgets, each currency on its own.

Your problem today

Invoices with no owner on any line.

Several provider invoices arrive at month end, each a single line per model. Splitting them by team means a spreadsheet and guesswork, and a runaway agent shows up as a surprise weeks after it started.

Life with Vidai

Cost within minutes

Every call is priced shortly after it's made, from the rate card or a price you entered. A call with no price is counted as unknown and said so, never shown as zero.

Owned, as it was then

Each call is charged to the team its key acted for at the time. Moving a team later never moves past calls.

One currency per amount

Euros and dollars sit side by side, never converted or added together.

Budgets that act

On the organisation, an environment, a team, an application, a person, an agent or a key: notify only, stop calls at the limit, or send calls to another model.

Bills you can close

Lock billing periods; late calls become adjustments on the first open day. Markups for chargeback, and exports for your finance systems.

Savings you can test

What-if shows what your real past calls would have cost on other models, before anyone changes a thing.

What you'll use

Your answers, in the Control room.

Money · Cost

Who spent what, against the period before.

By team, person or agent, application, environment, key, provider or model. Every figure opens the calls behind it.

Vidai Control room · Cost
Cost by team, with the period before beside it.
Cost by team, with the period before beside it.

Money · Budgets

Every budget, its spend and who it tells.

Each budget's spend against its limit, its state in an icon and a word, and the people it alerts at 50, 80 and 100%.

Vidai Control room · Budgets
Budgets for teams and agents, each with its limit, period and state.
Budgets for teams and agents, each with its limit, period and state.

Money · What-if

Test a cheaper model on your own calls.

Pick a model and see what last month's real calls would have cost on it, before routing anything there.

Vidai Control room · What-if
Comparing what past calls would have cost on other models.

Request logs

Every price, explained.

Each call shows how it was priced: quantity × rate = amount for every part, and where the price came from.

Vidai Control room · Request logs
How one call was priced, part by part.
How one call was priced, part by part.

The work Vidai takes on

A FinOps engineer and a cost pipeline: collecting usage, pricing it, attributing it, and keeping a price history that matches what was charged.

Re-pricing past calls after a late or corrected price, with a dry run first, comes with Enterprise. On Community, new calls use the price in force and calls already costed keep their cost.

Related

How we start together

Start with one team, on your own AI traffic.

After a 20-minute demo, we agree a two-week pilot with you: one app or team, your traffic, your infrastructure.
  1. 01

    Pick one app or team

    Point it at the Control room. One configuration change; nothing else changes.

  2. 02

    Watch for two weeks

    Every call priced, checked and recorded. Rules start in observe mode.

  3. 03

    See the evidence

    What it cost, what it caught and what it would have stopped, from your own traffic.