AI tools and agents
Seats today, consumption tomorrow
AI products rarely start where they end up. Charge seats while the shape is still settling, add a meter when consumption becomes the thing, and bill both on one document.
- Fixed
- Seats, priced per month
- Variable
- Runs, tokens or minutes
- Together
- One invoice, one approval
acme-agents · october
seats + meteredSeats
406.00USDC
14 × 29.00
Agent runs
2.48USDC
18,402
How it grows
From a seat price to a meter, without a migration
What the customer sees
- Fixed part
- Seats
- Variable part
- Metered
- Both parts
- One invoice
- For the customer
- One approval
Predictable for your customer and for your forecast.
Runs, tokens or minutes, recorded as your product produces them.
A single document with the figures that produced each line.
Bounded and revocable, covering the plan rather than each charge.
At the close
One document, both halves
Seats and consumption on the same invoice, each with the figure that produced it.
INV-00233
October period · Acme Agents
Opened when the period closed, collected against the approval already signed.
Questions
Before you price it
- Our usage is spiky. Will the approval cover it?
- The cap covers about twelve periods at the plan's amount, and a metered period can never collect more than it. Price the allowance so the usual month sits inside the cap, and the customer approves a figure they can see.
- Can we change pricing as the product changes?
- Yes. Prices are records in your catalog. Move a subscription to another price and the next period bills at the new one, without rewriting the integration.
- What do we record for an agent run?
- Whatever you charge for. The meter is yours; Reclack adds it up, puts the figure on the invoice and collects it.
Price it now, meter it later
Seats and consumption on one rail, collected in stablecoins from one approval.