API keys
How you receive your key, send it with requests, keep it safe and replace it.
Getting your key
Your key is created for your order and sent to your email as soon as your payment confirms. Each key carries its plan (Claude, ChatGPT or both) and its credit. We do not keep a copy of it, so store it somewhere safe right away.
Sending your key
Send the key in one of these headers. Both work on every endpoint; official SDKs pick the right one automatically.
| Header | Format | Typical client |
|---|---|---|
Authorization | Bearer <your key> | OpenAI SDKs, Codex, Cursor, Claude Code (ANTHROPIC_AUTH_TOKEN) |
x-api-key | <your key> | Anthropic SDKs, Claude Code (ANTHROPIC_API_KEY) |
curl https://api.evolved.to/v1/models \
-H "Authorization: Bearer $EVOLVED_API_KEY"This call is free. It confirms the key works and lists the models its plan includes. You can also check a key from the API page of your dashboard.
Keeping keys safe
- Store keys in environment variables or a secret manager, never in source code or version control.
- Never ship a key in a browser, mobile or desktop app bundle. Call evolved.to from your server instead.
- Anyone who has your key can spend its credit, so share it with no one.
- Never paste a key into a support message. We can find your requests by request ID.
Keys in the dashboard chat
The chat in your dashboard uses your key to talk to the models. The key stays in your browser: it is sent only with your own chat requests and is never saved on our servers. Choose whether this browser remembers it.
Replacing a key
Ask for a new key
Message support from the email address on your account. We send the new key to that address.
Deploy it
Update your environment variables or client settings and redeploy.
Confirm
Tell us once traffic has moved over, and we revoke the old key.