Pass your API key in the header for inference and /v1/models requests.
Authorization: Bearer everyais_your_api_keyYou issue keys from the dashboard. Only the SHA-256 hash is stored on the server, so once you leave the screen right after issuing a key you cannot see the plaintext again.
Per-key settings
| Setting | Description |
|---|---|
| Rate limit | 100 req/min by default. Adjustable when you create or edit the key |
| Monthly/daily/per-minute spend limit (USD) | 402 spend_limit_exceeded when exceeded |
| Allowed models | When set, calls to models outside that list return 403, and GET /v1/models results are filtered to that list as well |
| Scopes | chat · images · video · models:read. Calls outside a scope return 403. Leave them all empty to allow everything |
| Expiry date | When set, requests return 401 after expiry |
Authentication methods and account scope
The Anthropic SDK's x-api-key: everyais_... header is also accepted.
If both headers are supplied, a valid Bearer-formatted Authorization header takes precedence.
Keep keys in environment variables and make calls from your server, never from public browser code or repositories.
API keys authorize inference and reads for consumer accounts. Account settings, payments, and key management
require a signed-in user session; an API key returns 403 api_key_session_forbidden.
Supplier accounts cannot use consumer APIs (403 account_kind_forbidden).
Organization keys use the organization's credits and policies, including community supply and training-use consent. See model selection and access policies.