Skip to content

Users

Open User → Users. A user is the account entity in the gateway: it owns API keys, carries budget and billing period, and appears across operational views. You can set email, optional external identifiers, and budget-related fields.

The user detail page shows the budget plan, related API keys, external identity, and per-model Charged cost factors.

OctaFuse User Details showing budgets, API keys, external identity, and per-model Charged cost factors with the email redacted.
User Details keeps budget, keys, external identity, and per-model discounts together. The email is pixelated in this screenshot.
  1. On Users, filter by email, external identity, or status. Each row summarizes spent versus maximum budget, the next reset, active versus total keys, and model factors.
  2. Create a user: fill email, optional external system and user id, budget caps/base, billing period, optional metadata (usually JSON for your own labels), and per-model factors when needed.
  3. Review a user: open the detail view to check budget and keys; under Charged cost factors, select catalog models and enter their factors.
  4. Issue keys: create keys under API keys for this user, or use the external-identity path in the key wizard.

The user factor is applied after the route’s user charge:

Final user charge = catalog standard price × route Charged factor (including schedule override) × user model factor

FactorTypical meaning
1Keep the price calculated by the route
0.820% discount
0.550% discount
0No charge for this model and user

Models not listed remain unchanged. The factor changes only final user charge and budget usage, not catalog price or supplier cost. It applies to LLM, Images, and Audio, but not independently priced Agent Tools.

Automation can write charged_cost_factors through the Admin API as { "<model id>": factor }. Unknown model ids, negative values, and invalid objects are rejected; null or an empty object clears existing factors.

After signup, your backend can call the Admin API to create users, set model discounts, and issue keys — see Integration and the GitHub technical reference.