Skip to main content
Create, use, rotate, and revoke API keys from the dashboard or the API. Keys let servers and CLIs call the Aria Compute gateway and download authenticated model bundles.

When to use an API key

Use an API key for server-to-server calls that hit the gateway or the model download endpoints. Use a session JWT for user-scoped actions in the dashboard API (billing, account settings, session management).
1

Open the API Keys page

Sign in and open /dashboard/api-keys (or the equivalent on ariacompute.cn).
2

Create a key

Click Create, enter a descriptive name (for example production, ci, or laptop), and submit.
Copy key immediately. It is only returned in this response; the dashboard and future GET /api/api-keys calls show only the prefix.
3

Use the key

Send the full value as a Bearer token to the gateway or download endpoints.
4

List keys

Returns each key’s id, name, prefix, created_at, and last_used_at.
5

Revoke a key

Returns 204 No Content. The key stops working immediately.

Rotation

Rotate keys periodically or whenever a key may have been exposed:
  1. Create a new key and store it in your secret manager.
  2. Deploy the new key alongside the old one.
  3. Wait until logs confirm all traffic uses the new key.
  4. DELETE the old key.

Per-site keys

API keys are scoped to the site that issued them. If you use both ariacompute.com and ariacompute.cn, create a key in each dashboard and use them against the matching gateway.
Give keys meaningful names. A short prefix plus environment (prod-api, staging-worker) tells you which one to revoke.
Never commit API keys to source control or paste them into client-side JavaScript. Anyone who has the key can drain your wallet.