Account & billing
Account, API Keys, and usage
Dashboard is the source of truth for accounts, Keys, balance, and billing; the model gateway only handles Key-authenticated model calls.
Register or sign in, manage API Keys in Dashboard, and follow the model, balance, usage, and optional purchase entry points currently shown there.
- Identity
- Methods enabled in Dashboard
- Keys
- API Keys page
- Billing
- Runtime settings
- Usage
- Dashboard records
Registration and sign-in
- 1Open the Dashboard registration or login page.
- 2Use an authentication method currently enabled on that page.
- 3Manage the account and API Keys after signing in.
- 4Sign in again when the session expires; the public site stores no account state.
Balance and purchases
- 1Sign in to Dashboard.
- 2Review the balance, model rates, and any enabled purchase entry point.
- 3When adding balance, use only the entry point currently shown in Dashboard.
- 4Return to Dashboard to verify balance and Usage.
| Information | Source of truth |
|---|---|
| Balance | Current Dashboard value |
| Purchase methods | Current Dashboard options, when shown |
| Model rates | Runtime configuration |
| Request costs | Usage records |
Review balance and records
| Page | Purpose |
|---|---|
| Account overview | Review account and current balance |
| Purchases and orders | Use and review only when enabled |
| Model pricing | Review current model rates |
| Usage records | Review requests, tokens, and costs |
Fields, units, and states are defined by the current Dashboard; public docs do not duplicate its internal data model.
Manage API Keys
| Operation | Guidance |
|---|---|
| Create | Use the Dashboard form and store the result safely |
| Copy | Paste only into controlled Secrets or user-level config |
| Update | Verify new configuration before removing the old one |
| Delete | Remove only after no client uses the Key |
- Keep full Keys out of URLs, frontend bundles, logs, and public repositories.
- Use separate Keys by environment for isolation and revocation.
- Available operations and limits follow the current Dashboard.
Usage records and statistics
| Information | Purpose |
|---|---|
| Request ID | Correlate one call during diagnosis |
| Model | Confirm the model ID used |
| Tokens | Review input, output, and aggregate usage |
| Cost | Review the actual amount shown by Dashboard |
| Time and outcome | Locate the request and determine its result |
Column names, units, filters, and statistics follow the current Dashboard. For diagnosis, keep the request ID, time, model, and outcome.
Account security
- Enter account credentials only in the official Dashboard.
- Keep the full Key out of URLs, browser storage, logs, analytics, and public repositories.
- After suspected exposure, create a replacement, update clients, and delete the old Key.
- Purchase only from information currently shown in Dashboard.
- Sign out on shared devices.