Customers
Customers lists everyone your engines meter in the current mode: users, orgs, agents, or any type your policy uses. They appear as your app creates them through the SDK, or when you add one with New customer. Changes you make here reach your connected engines.
Finding customers
Search by ID or name, filter by plan and type, and sort by recently active, newest, or ID. Usage columns adds up to six metered entitlements to the table. With a segment selected in the top bar, only its customers show. The list stays live: with no search or filter, new customers appear at the top as your app makes them.
One customer
A customer's page shows:
- Usage and limits: each entitlement this period, with a bar against its limit, what happens past it, and when it resets. Tags show where it differs from the plan (given, taken, override).
- Usage over time, by day, for each metered entitlement.
- Features: the on or off entitlements they have.
- This period: usage, overage, and your cost per entitlement, what's been billed so far, the projected bill, and the margin.
- Invoices and payments, Balances (grants and caps), Related customers (an org and its users), Metadata, Plan history, Recent denials, and Activity.
Changing a customer
These need the Change customers permission (see Team), except deleting. Customers start on Pay as you go.
| Action | What it does |
|---|---|
| Change plan | Moves them to another plan, keeping or starting over this period's usage. Charges for the change (Ex. prorated seats) follow your plans' billing settings. |
| Override the limit | One customer's limit, mode, or end date for an entitlement, without a new plan. Ex. 250,000 requests instead of 100,000 for a deal. Remove the override goes back to the plan. |
| Give an entitlement | An entitlement their plan doesn't have, from another plan (optionally until a date), or back after it was taken. Ex. SSO for a two-week trial. |
| Take it away | Turns off an entitlement their plan has, keeping its usage. Ex. pause exports while an invoice is unpaid. |
| Adjust usage | Adds to, removes from, or sets a meter, Ex. to correct a mistake. |
| Add a topup | A topup from their plan, given at no charge or charged to them. |
| Add a cap | A ceiling on what they spend or what they cost you, monthly, weekly, or for good. It can deny past the ceiling, or only record and notify. |
| Edit name, type, and IDs | Their name, type, the customers they refer to (Ex. a user's org), and other IDs your app knows them by. |
| Metadata | Key and value fields on the customer, which segments and dashboards can use. |
| Delete customer | Removes them from Limitr Cloud with their meters and balances; invoices and payments are kept. If your app uses them again, it creates them again. Needs Delete customers. |
You can also ask Dot ("give Acme SSO until the end of the month"): it proposes the change on a card, and nothing changes until you apply it. Dot can't adjust usage or delete customers. See Changes you apply.
For how these work in the engine, see Trials and custom deals and spend caps.
Custom prices
On Enterprise, Custom prices sets a price for one customer in place of the list price (a percent change, a flat change, or a new price), Ex. a negotiated rate on AI tokens. For a group of customers, use a pricing rule on a segment instead.
Billing a customer
Invoices close at the end of each period and are charged through your connected Stripe account. On a customer's page, Billing settings (with the Manage billing permission) can turn on manual billing or ask for approval before charges, for that customer only. A payment waiting for approval has Approve; a failed one has Retry.