Authentication
Every request carries an API key in the standard Authorization header. Keys belong to one account and spend that account's credits.
Authorization: Bearer du_live_...Create a key
- A paid account is required. Minting is refused with
403until the account has bought credits. - Open Profile → API keys and create a named key.
- The full key is displayed once. Store it in an environment variable or a secret manager.
- Up to 10 active keys per account. Revoking is immediate for new requests; jobs already running keep running.
How a key is checked
- The bearer token must start with
du_live_. - The key is validated on every request.
- A missing, malformed, unknown, revoked, or removed-account key all return the same
401 unauthorized. - Each key reports its last-used time on the profile page.
Revoke
Use the revoke button on the profile page. Revoking is idempotent; a second revoke of the same key is harmless. A key that belongs to another account is reported as not found.
Keep it server-side
The API sends no CORS headers. It is built for servers, scripts and local agents, not for browser code. A key in a bundled web or mobile app is a public key.