# Console

> Tokens, balance, usage and top-ups — the few things you do once in the console.

The console owns everything account-related: sign-in, tokens, usage and top-ups. These docs skip the
tour and cover only the places people get wrong.

## Tokens

- **Create one**: Tokens → Create. Pick a group (which decides available models), a quota cap and an
  expiry
- **Shown once**: copy the token immediately; the full value disappears after a refresh
- **Deletion is instant**: if you suspect a leak, delete and recreate — no waiting period

## Balance and top-ups

- Balance is denominated in USD; at zero, requests are rejected and resume as soon as you top up
- A token's quota cap is a **soft cap** — it constrains only that token, not others on the account

## Usage

The usage page splits by model and by token. Answer two questions first:

1. Which kind of call accounts for most spend? (usually long context plus high output)
2. Is any single call unusually large? (typically a whole document pasted into the prompt)

## Common tasks

| Goal | Where |
| --- | --- |
| Get the first key | Tokens → Create |
| Cap a project's spend | Tokens → Edit → quota cap |
| Disable a key | Tokens → Delete |
| Check a day's spend | Usage / Logs |
| Top up | Wallet / Top up |

<Callout type="info" title="Sign-in and sign-up">
Sign-in and sign-up are served by the console, a separate site from these docs. Every "key" mentioned
here means an `sk-` token created in the console.
</Callout>