GET STARTED
Authentication
Every API request is authenticated with an ar-… key in the Bearer header.
API keys
Create a key in the Keys section of your dashboard. The full secret is shown once — store it safely. Keys belong to the account (organization), not a user: all spend draws from the shared account balance.
!
Never embed a key in a frontend or mobile app. Keep it server-side; proxy through your own backend for browser use.
Request header
Scopes
When creating a key you can restrict it to a set of surfaces:
chat— access to /chat/completions.images— access to /images/generations.videos— access to /videos.
A key with no scopes selected has access to all surfaces. A request to a surface outside the key’s scopes returns 403 permission_error with code insufficient_scope — the key is valid, it just lacks the right.
Revocation
Revoke a key from the dashboard at any time — it stops working within a second. To rotate, issue a new key, switch your service to it, then revoke the old one.
NextParameters →