Why do API businesses lose money even when their gateways are busy? Because traffic is not revenue. When a customer asks your AI for something computationally expensive, you burn upstream processing power first — and only hope the customer’s card clears later. If the invoice is declined, you already paid the provider. That gap is an API revenue leak.
The short video below walks through how Finno closes it on every request.
What the video covers
The leak: usage first, money later
Most stacks let the gateway forward the call, then bill asynchronously. That works until volume, retries, and payment failures collide:
- Upstream returns 200 and you owe the provider.
- Token count was unknown while the model was generating.
- The customer’s card fails — invoice declined.
- Your margin absorbed the cost of someone else’s free inference.
Revenue did not “disappear in accounting.” It was never secured on the request path.
Enter Finno: a vault on the hot path
Finno sits between the User Node and Upstream AI as a proxy that acts like a vault. Every API request passes through it — not as an after-the-fact usage event, but as a funded, metered, ledgered transaction.
The catch: tokens are unknown while generating
For token-metered AI APIs, you cannot know the exact cost until the model finishes. Billing only after the response is how leaks open. Finno’s answer is a two-phase money protocol:
- Reserve — before a single token is generated, Finno locks worst-case funds from the consumer’s balance (quota, wallet, or credit). Insufficient funds → the upstream is never contacted.
- Finalize — when the AI returns, Finno meters the actual tokens, settles the exact charge, and refunds any unused hold back to the user.
In the walkthrough: Finno locks a hold while tokens are still ???; after 840 tokens the cost finalizes at $10, the unused hold is released, and the user balance settles at $90. The ledger posts the same moment: $8 owed to the upstream provider and $2 margin.
Double-entry, not a usage spreadsheet
Finalize does more than debit a wallet. It posts a double-entry split so cost of goods and margin are born together:
Wallet (−$10) = Owed (+$8) + Margin (+$2)Provider cost and your take are secured in the same step as the HTTP response. There is no overnight job hoping to reconstruct what happened. Revenues are secured — leaks become nothing.
Who should watch
- Founders and CFOs of AI/API platforms watching margin leak into unpaid upstream spend
- RevOps and finance teams tired of reconciling gateway logs against invoices
- Platform engineers designing prepaid or credit-metered AI products who need Reserve/Finalize in practice
Dig deeper
- Closing the billing gap — why proxy and ledger must be one system
- Secure every B2B transaction — revenue assurance per request
- How it works — the full request-path money protocol
- Talk to us — map Finno onto your commercial model