Introducing Recovea: the financial layer of AI
The AI-spend gateway is open: see, control, and prove every dollar your AI spends, with your own keys, starting free.
Today Recovea is open to everyone. It is an AI-spend gateway: a thin layer between your code and your model providers that meters every request, enforces your budgets, and writes a receipt for every dollar. The integration is one line: point your client's base_url at api.recovea.ai and keep your own keys. We never resell tokens, and your traffic still goes to the provider you chose, under the key you own.
We built this because AI spend became real money faster than the tools to govern it. Finance sees one number at month end. Engineering sees a dashboard that cannot answer which key, which route, which customer. Nobody holds a receipt. The missing piece is not another optimizer. It is boring, structural financial infrastructure in the request path.
What is live today
- The gateway. OpenAI-compatible and designed to fail open: if Recovea degrades, your traffic goes straight to the provider. Overhead today is ~1ms p50 / 2ms p95 local gateway overhead (measured July 2026, non-production), a benchmark of the gateway hop rather than a production percentile; we will publish production numbers once we have them, not before.
- The meter. Every request metered live across providers (model, tokens, cost) while it happens, not at month end.
- Receipts and the ledger. A per-request receipt and a hash-chained ledger you can re-derive offline. You do not have to trust us to check our math.
- Caps and the kill-switch. Budget alerts at 50, 80, and 95 percent, and hard caps that act rather than notify.
- Attribution. Spend broken down per key, per project, and per route, so the bill finally has names on it.
- The free scan. Point it at your billing data and get a teardown of where the money goes, with the method shown alongside the result.
The free tier is capped at 100 requests/min and 200K tokens/min. Paid plans start at 600 requests/min and 1M tokens/min, rising to 3,000 requests/min and 5M tokens/min at the top of the ladder. Rate limits are indicative, never a guarantee: the limiter runs inside each gateway process, so the throughput you actually get can land above or below the published figure. Starting is free and takes no card.
What is deliberately off
Two things you might expect from a company like ours are switched off on purpose.
Verified savings are off. Every savings figure Recovea produces today is measured (a counterfactual computed against the provider's own reported numbers), and it is labeled "measured · not applied." Calling a saving verified would require proving that quality was preserved, and that requires an evaluation gate calibrated on real production traffic. Ours is not calibrated yet. Until it is, the word verified does not appear next to a savings number anywhere on this site.
Gain-share is off · proof pending. We will not charge a percentage of savings we cannot yet stand behind. Routes default to observe; optimization levers are activated with your sign-off, never silently.
The referee takes no money from the players
Recovea is BYO-key. No token markup, no reselling, no provider money. If the referee is paid by a player, the score is marketing. The subject of the proof never pays for the verdict. That neutrality is the product, and it is why the ledger is designed to be checked without trusting us.
What we will publish, and how
You may notice this launch post contains no savings percentage. That is deliberate: we do not have a production-calibrated number, so there is no number. Here is what will stand where a percentage would normally go. Starting in phase 1, this blog publishes a weekly number: gateway overhead measured in production, and cache-alignment savings on opted-in routes measured against the provider's reported cached_tokens, each with its methodology one click away and its known limits stated in the same post. When a week's number is bad, it publishes anyway.
The ask
Run the free scan on your current bill. It costs nothing and the method is public. If you like what it shows, point one route's base_url at us and watch your real spend go live in under ten minutes, free, no card. The receipts start with the first request.