Recovea

The Financial Layer of AI. See, control, and prove every dollar your AI spends.

[Recovea @RecoveaAI]

We're launching Recovea. Our mission is to make every dollar AI spends visible, bounded, and provable.

Every number you see about AI money today comes from a party with a stake in it — the provider that bills you, the gateway that takes a percentage, the platform that resells the tokens. We're building the alternative: a neutral layer in the request path that enforces your limits before the money leaves, and writes a receipt you can check without trusting us.

[Recovea @RecoveaAI]

We shipped four things for teams spending money on AI.

• Meter: metering that is not owned by the party sending your bill.
• Cap: refuses the request before your provider is ever called. Not an email afterwards.
• Breaker: a dollar budget that one agent run carries. The run dies at the line, mid-run.
• Prove: a receipt for every request, which you can re-derive yourself.

All four are live today, on every plan including Free.

The last one is the one we care most about. You should not have to take our word for any number we put on your screen.

https://t.co/ctwqMu1CV6

[Recovea @RecoveaAI]

Two updates shipped today.

You set a cap on an API key from the key's own row now. No key id to copy from somewhere else. And a key can be born with one, offered under the secret when you mint it.

And every limit you have, on the organization and on every key, is on one page: what it used, what is left, when it resets.

https://t.co/V9mCxr1GBN

[Recovea @RecoveaAI]

Two million Hacker News comments, read fourteen ways. The most repeated request in fifteen years, in the same words: a hard cap, not an alert.

[Ken Barlow @knbrlo]

24 million tokens on research yesterday, reading 2 million Hacker News comments about what people are actually asking for and paying for with AI.

1. Nobody is asking for a better model. They're asking for a predictable bill.

2. The money goes missing at the seams, not in the rate card.

3. The sharpest objection to anything in the request path isn't latency. It's who can read the traffic.

[Recovea @RecoveaAI]

What's live today: hard caps enforced in the request path — the request that would cross your line is refused before the provider is contacted. A receipt for every request you can re-derive yourself. Your own provider keys.

Honest scope: API traffic only, and a cap is a stop, not a ceiling.

Free tier, real cap, no card. https://t.co/VKbmT38f0H

[Recovea @RecoveaAI]

We're launching Recovea. Our mission is to make every dollar AI spends visible, bounded, and provable.

Every number you see about AI money today comes from a party with a stake in it — the provider that bills you, the gateway that takes a percentage, the platform that resells the tokens. We're building the alternative: a neutral layer in the request path that enforces your limits before the money leaves, and writes a receipt you can check without trusting us.