Authentication
Gateway API requests authenticate with Accly API keys.
Create an API key
API keys are created in the Accly app:
- Open chat.accly.net .
- Open settings and go to API Keys.
- Create a key with a name you will recognize.
- Optionally choose specific models, a USD spending limit, or an expiration time.
- Copy the key from the masked row using the copy action.
The secret is encrypted at rest. The API Keys table shows only a masked preview, while an authenticated copy action retrieves the reusable secret when you need it.
Plan requirement
API keys are available on paid plans: Starter, Pro, and Max.
Free does not support API keys. If a paid subscription is suspended or the account is restricted, the gateway rejects API requests from existing keys.
Authorization header
Send the key in the Authorization header:
Authorization: Bearer sk-your-accly-api-keyBearer authentication is the general example used in this guide. Clients that require a native key header can send the same Accly key as x-api-key or x-goog-api-key; the target model and endpoint must still support that protocol.
Example:
curl https://api.accly.net/v1/chat/completions \
-H "Authorization: Bearer sk-your-accly-api-key" \
-H "Content-Type: application/json" \
-d '{
"model": "claude-opus-4-7",
"messages": [{"role": "user", "content": "Hello"}]
}'One key, supported endpoint families
An Accly key can authenticate supported OpenAI-compatible, Anthropic, Google, embedding, rerank, and audio routes. Your client chooses the wire format; the selected model must implement that endpoint protocol. See Gateway API and Models before configuring an SDK.
When creating or editing a key, an empty model selection means all models. You can instead select a specific model allowlist and search by model name or ID. Requests for models outside that allowlist are rejected by the gateway.
Paid plans support up to 85 keys per account. Every key must have a name. You can pause or resume a key with its active switch, permanently delete it, or let an optional USD spending limit and expiration disable it automatically.
Keep keys secret
Treat Accly API keys like passwords.
- Never expose API keys in browser code or mobile client bundles.
- Do not commit keys to Git.
- Store keys in server-side environment variables or a secrets manager.
- Use separate keys for separate apps or environments when possible.
- Revoke keys you no longer use.
Rotate a leaked key
If a key is exposed:
- Disable or delete the key in the Accly app settings.
- Create a replacement key with a new name.
- Update your server, tool, or automation configuration.
- Review recent usage for unexpected activity.
Revoked keys are rejected by the gateway.