Skip to content

Quotas, pricing and discounts

Quotas determine how much a user can consume; pricing determines the charge for a request. Check the billing currency and business timezone in System configuration before setting quotas and discounts.

Periodic budgets and permanent wallet credit

Section titled “Periodic budgets and permanent wallet credit”
PoolTypical useConsumption and resets
Periodic budgetDaily, weekly or monthly plansResets under the user’s budget rules
Permanent walletTop-ups, signup credit, refunds or compensationDoes not reset with a subscription period

Requests consume the periodic budget first, then the wallet for any shortfall. A user with a zero periodic cap can still call when the wallet has credit. An unlimited periodic budget can produce an unlimited total remaining value.

Separate periodic budget and permanent wallet credit

Use the Admin wallet credit operation for top-ups, with a unique business reference for idempotency. Do not repeatedly increase the periodic cap to distribute purchased credit. See the Admin API.

  • Standard: catalog pricing with the active official model schedule.
  • Metered: the request’s calculated supplier cost.
  • Charged: the amount charged to the user and deducted from quota.

Routes configure Charged and Metered factors separately. A Provider factor applies to both while valid, without changing Standard. Keep official model schedules separate from route schedules. Preview prices before saving, then inspect the request’s recorded snapshot in logs.

A user may have one factor per model or different factors per route group. An exact group takes precedence over *; no match leaves the route price unchanged.

USER_CHARGED_COST_FACTOR_MODE selects composition:

ModeRuleRoute factor 0.8 and user factor 0.5
multiply (default)Multiply the factorsFinal factor 0.4
minUse the smaller factorFinal factor 0.5

The user charge is based on the current official catalog price × the composed Charged factor. A user discount does not change supplier cost. See the user API and billing reference for exact rules.

Model and route-group user discounts

Models and tools use different pricing rules

Section titled “Models and tools use different pricing rules”

Text and embeddings generally use tokens. Images use token or per-image pricing; audio can use tokens, duration or characters. Usage depends on the model and adapter.

REST and MCP tools have their own standard price and factors. Model route schedules and per-model user discounts do not apply. MCP currently bills successful tool calls per request; REST search uses requests and AI detection uses configured character units.

  1. Review both quota pools and model/group discounts on the user.
  2. Send a request with Simulator or a real client.
  3. Check Usage and accounting in the request flow, then the two quota changes in Audit Logs.
  4. Call authenticated GET /v1/me to confirm the remaining amounts.

Users · Account audit · Routing