# Dashboard Guide

Sign in at [qcode.cc](https://qcode.cc) and open the console at
[qcode.cc/dashboard](https://qcode.cc/dashboard). The console sums itself up in one line —
*"Manage your API keys, top-up and usage"* — and it is a single page: keys, balance, plans,
usage, referral rewards and support all live on it.

> Not sure what a QCode key is versus a Claude / ChatGPT subscription? Read
> [Subscriptions vs API Keys vs QCode Keys](/docs/reference/subscription-vs-api-key) first.
> Outside mainland China? Start with [QCode for Users Outside Mainland China](/docs/getting-started/international-users).

## What the console contains

| Block | What you do there |
|---|---|
| User bar (top right) | See your sign-in email and `ID: …`, the balance in both currencies, and the **Recharge** / **Buy Plan** buttons |
| API Access Address | Copy the address that goes into `ANTHROPIC_BASE_URL` / `base_url` |
| API Key Management | Create a key, reveal and copy its value, renew it, unfold expired keys |
| One-Click Setup (inside each key card) | Copy the install command for Claude Code or Codex |
| Open API | Manage the read-only access token that reports your keys' expiry and usage |
| Usage Statistics | Quota consumption per active key, plus monthly totals |
| Docs & Resources | IDE integrations and popular guides |
| Service Guide / Referral Rewards / Quick Links | Operating rules, your referral link, reward claiming, help articles, error codes, support hours |

## API Access Address

The block is titled **API Access Address** and every row has its own copy button. **Which row is
highlighted as recommended depends on the language of the console you are signed in to**:

- **Chinese interface** — `https://asia.qcode.cc/api` is highlighted as the recommended row, and
  the note *"Mainland China users should use the accelerated address; others use the global
  address. Both offer identical performance"* is shown under it.
- **Any non-Chinese interface** (currently English, Japanese, Russian) — `https://api.qcode.cc` is
  highlighted, and the rows under it are labelled **Backup** (USA: `https://us.qcode.cc/api`, Asia:
  `https://asia.qcode.cc/api`).

The address you copy still has to carry the right **path prefix** for the tool you use — see
[Endpoints & API Paths](/docs/getting-started/endpoints-and-api-paths). For Claude Code the pair
looks like this:

```bash
export ANTHROPIC_BASE_URL="https://api.qcode.cc/api"
export ANTHROPIC_AUTH_TOKEN="cr_your_key"
```

## API Keys: create, view and copy

**API Key Management** is the block with the **Create Key & Activate Service** button. If you have
no key yet, the empty state spells out the order of operations: **Top Up Balance** → **Buy a Plan**
→ **Start Using**.

1. Top up on [qcode.cc/recharge](https://qcode.cc/recharge) (see
   [Payment Methods Overview](/docs/reference/payment-methods)).
2. Pick a plan on [qcode.cc/subscribe](https://qcode.cc/subscribe) — either **Recommended Plans**
   or **Custom Configuration** — and confirm. A successful purchase states
   *"Subscription Activated — Your API Key is created and ready to use"* and shows the key with a
   copy button and a **Go to Dashboard** link.
3. Back in the console, the key value is **not printed by default**: the row shows *Loading…*
   until you press the eye button to reveal it, then **Copy**. If you copy before the value has
   loaded, the console tells you so instead of copying an empty string.

Other things on the same block:

- A freshly ordered key can show *"API key is being activated, we will process it as soon as
  possible"* with a link to online support.
- A key you already own can show a **Renew** button (a quick renewal priced from your balance).
- Keys that ran out appear under the collapsed **Expired keys** list, marked
  *Key expired or disabled*.
- Each card links the three clients one key serves: Claude, Codex and Gemini.

## One-click setup commands

Every active key card carries a **One-Click Setup (Recommended)** block with a **macOS / Linux**
and a **Windows** tab, one command line for Claude Code and one for Codex, each with its own
**Copy** button:

```bash
curl -fsSL https://qcode.cc/install/claude-code.sh | bash
curl -fsSL https://qcode.cc/install/codex.sh | bash
```

The console's hint under the block: *"Paste your key above when the script prompts for it."* On the
Windows tab the commands are the `irm … | iex` equivalents, and a collapsed section underneath adds
a CMD one-liner and a downloadable launcher for machines where `irm` is unavailable or blocked by
the execution policy. The full walkthrough,
including how to force the script's interface language, is in
[One-Click Setup Script](/docs/getting-started/one-click-install).

## Usage Statistics

The **Usage Statistics** block is keyed to your active key (*"Quota usage for current active key"*)
and can auto-refresh on a timer (Off / 5 / 10 / 30 / 60 minutes) or on demand with **Refresh**.

| Section | What it reports |
|---|---|
| Daily Cost Limit | The maximum spend per day; it resets at midnight Beijing Time, and the API pauses when it is reached and resumes the next day |
| Time Window Limit | Request count and cost inside a rolling 4-hour window. Personal plans *"removed the 4h rate window entirely in July 2026 — only the daily limit remains"*, so this section can read *No window limit* |
| Opus Weekly Limit | A separate weekly allowance for the Opus tier, resetting every Monday (Beijing Time); plans without Opus access say so here |
| Monthly Usage Overview | Total Tokens, Total Requests, Total Cost — counted from the day the key was created |
| Today's Model Calls | Per-model input / output / cache-write / cache-read tokens for the current day |
| Booster | Whether a booster pack is active; see below |

The panel's own disclaimer: *"Data shown here may have slight variations, actual limits are based
on Claude Code responses."* For a rough per-session figure use `/cost` inside Claude Code, and for
how the money is calculated see [Billing Description](/docs/reference/billing).

## Top-up, plans, boosters and upgrades

- **Balance is per currency.** *"CNY and USD balances are separate. Recharge amount will be added
  to the corresponding currency balance."* The user bar shows both figures side by side.
- **Top-up limits** shown on the recharge page: minimum **¥100** for CNY, minimum **$1** and
  maximum **$2,000** for USD, plus per-method caps that the page explains when you hit them.
- **Coming back after a top-up**: the console banner reads *"Balance received — You can activate a
  plan now."* with a **Choose a plan** button. Any leftover is not lost — *"Any balance left after
  your top-up isn't wasted: use it later toward an upgrade or a booster pack."*
- **Multi-month purchase** is discounted: *"Subscribe for 3+ months for up to 25% off (12
  months)."*
- **Booster packs** (*Self-service Booster Pack*) can be bought from the console with balance and
  expand your quota immediately; they reset at 2 AM Beijing time (UTC+8).
- **Upgrades** are not a console button: buy the higher plan first, then mail
  [hi@qcode.cc](mailto:hi@qcode.cc) so the old one is closed and its unused value is credited back
  to your balance.

## Sub-keys and team features

The personal console manages **one main key per plan** — there is no self-service sub-key screen in
it. Sub-keys are part of the team products:

- The **Enterprise Team Edition** page describes a *Sub-API Key Management Center* with
  *"fine-grained configuration and management for each team member"*, and the plan comparison table
  lists *unlimited sub-keys, each with its own quota*.
  That edition also lists **Bank Transfer Supported**, **Official Invoices Available** and **Custom
  Service Agreements**. Steps: [Enterprise Team Guide](/docs/reference/enterprise-guide).
- On the subscribe page the team card advertises *"Flexible quota & sub-key mgmt"* and points to
  [hi@qcode.cc](mailto:hi@qcode.cc).
- The console itself only offers team **orientation** — a **Team / Enterprise** entry in the welcome
  dialog and a *Team Features* dialog for the Max X20 team edition ("Multi-account management for
  team collaboration", "Customized service…", "Dedicated technical support…").
- **Resellers** get a separate Partner Dashboard with sub-key issuance, covered in
  [Partner Open API Guide](/docs/reference/partner-api).

## Open API access token

The **Open API** card says: *"Use an access token to query your API keys' expiry and daily usage
programmatically."* **Manage token** opens `/dashboard/openapi-token`, where you can generate,
reset or revoke the token:

```bash
curl -H "Authorization: Bearer qot_..." \
  https://qcode.cc/api/v1/openapi/keys
```

- Two read-only endpoints are listed on that page: one for all your active keys' expiry and usage,
  one for the account-level usage summary.
- The token is shown **once**: *"Your new token (shown only once) — copy it now"*, and *"We store
  only a hash — if you lose it, reset to get a new one (the old token stops working immediately)."*
- Reset and revoke both ask for confirmation, and revoking disables Open API access until you
  generate a new token.

## Support and ordering questions

- The console's **Support** line: *"Weekdays 10:00 - 21:00 (UTC+8) online response"*, with
  off-hours messages *"checked intermittently, replies may be delayed"*, and *"Email available
  anytime: hi@qcode.cc"*.
- Live support is the **Contact Us** button in the bottom-right corner (Telegram or email).
- **Request Urgent Processing** explains the wait: new upstream accounts take one to two hours to
  apply and configure during business hours.
- Quick Links also holds **Usage Help** (the knowledge base) and **Common Error Codes**; for
  symptoms and fixes see [Troubleshooting Guide](/docs/reference/troubleshooting) and
  [Error Code Reference](/docs/reference/errors).

## Related Pages

- [Payment Methods Overview](/docs/reference/payment-methods) — which rails top-up accepts
- [Billing Description](/docs/reference/billing) — how usage turns into money
- [Endpoints & API Paths](/docs/getting-started/endpoints-and-api-paths) — the address plus path prefix
- [Environment Variables](/docs/getting-started/environment) — where to put them
- [One-Click Setup Script](/docs/getting-started/one-click-install) — what the console's commands do
- [Subscriptions vs API Keys vs QCode Keys](/docs/reference/subscription-vs-api-key)
- [Enterprise Team Guide](/docs/reference/enterprise-guide) — sub-keys and invoicing
- [Partner Open API Guide](/docs/reference/partner-api)
- [FAQ](/docs/reference/faq)