Usage based billing for API products.
Charge by tokens, calls or credits, sell prepaid balances that top up on their own, and send an invoice with the usage attached. Customers pay through your own Stripe or PayPal account.
From $39 a month, never a percentage of what your customers pay. We never hold your money.
- Sep 1 Bought $99.00 of credits, $2.50 per million tokens.
- Sep 18 Balance dropped under $20. Topped up $99.00 automatically.
- Sep 24 38 million tokens so far this month, $95.00 of credits.
- Oct 1 Invoice goes out with the usage attached.
One account's month. The balance topped itself up.
An AI product's month of usage, metered to invoice, in 46 seconds.
Lumen AI stops adding up usage from logs and bills every token once, with the usage on the invoice.
Payments run through the accounts businesses already trust
Stripe
PayPal
GoCardless
Adyen
Paystack
Flutterwave
Authorize.Net
Braintree
QuickBooks
Xero
HubSpot- Slack
The four things that matter when you bill by use.
Prices the way model cards quote them
$2.50 per million tokens, not a decimal with six zeros. Meter input and output separately if you price them separately, and round once, on the invoice line.
Prepaid credits that top up themselves
Sell a balance, burn it down per request, and top it up automatically when it drops under a threshold the customer chose. No surprise invoice, no interruption.
Pay as you go with an allowance
A base plan with a million calls included, then a rate per thousand above it. Usage sent twice is counted once.
The invoice shows the usage
Every invoice carries the meter reading behind each line, so the customer's finance team stops asking and your support inbox gets quieter.
How an AI product with 212 accounts runs on yRecurring.
Lumen AI sells access to a model per million tokens, with prepaid credits for smaller accounts. Usage was added up from logs at month end, invoices went out late, and a retry in their pipeline once billed a customer twice.
- 01$2.50 per million tokens, input and output metered separately, and prepaid credits that top up under $20.
- 02Usage sent as it happens with an id on every record, so a repeat is counted once.
- 03212 accounts and 150 balances imported between deploys.
- Invoices go out on the 1st with the usage attached. The "what is this line?" emails stopped.
- Balances top themselves up; no account has been cut off in the middle of a job.
- The double charge cannot happen again.
What your customers see.
A checkout page you share or embed, and a place where they see their invoices, update a card, or change plans without emailing you. Your logo, your colors.
Move your accounts over between deploys.
Export your accounts and balances from the tool you use now as a spreadsheet, upload it, and check the preview line by line. Nothing is written until you approve it, and no customer gets an email about an old invoice. Balances and renewal dates carry over.
Why trust us
Payments run through your own Stripe, PayPal or bank debit account. We never hold it, and card data never touches our servers.
From $39 a month. Never a percentage on any plan, so you keep every dollar of growth. See pricing
Your data exports any time, in open formats, and your price is locked for two years. How we keep it safe
Before you move a single customer.
Can I price per token?
Yes. Enter the price per million tokens the way a model card quotes it, meter input and output separately if you like, and the invoice rounds once per line.
Can customers prepay?
Yes. A prepaid balance that burns down per request and tops itself up when it drops under a threshold the customer chose.
What if my system sends the same usage twice?
It is counted once. Each usage record carries an id, and a repeat with the same id is ignored.
Can I mix a subscription and usage?
Yes. A base plan with an allowance and a rate above it, on one subscription and one invoice.
Am I locked into a contract?
No. Self serve plans are month to month, and you can export every account, balance and invoice any time, in open formats.