The operating problem
Usage billing fails when raw traffic, customer entitlements, late events, credits, and locked invoices can drift or be rewritten without an audit trail.
The intended control surface
This capability is part of the reviewed product architecture, not a decorative console module.
- Versioned plans and entitlements
- Idempotent append-only usage events
- Credits, corrections, and invoice locking
- Manual invoicing plus optional payment adapters
What exists today
Producer-managed API products, client subscriptions, plan rate limits, and exact durable quota admission are implemented. Usage-priced products, credit and correction ledgers, invoice locking, and provider-neutral API monetization payment adapters are not yet implemented.
Work with the implementation team
Reallexi is accepting architecture conversations with teams whose requirements can shape this production slice. An inquiry does not imply that an unshipped feature is available.
Frequently asked questions
Is this capability generally available?
No. The page describes a reviewed implementation direction. The current capability boundary is stated above and in the public changelog.
Can Reallexi evaluate our requirements?
Yes. Use the enterprise inquiry form without including credentials, private payloads, or regulated data.