Authentication

Every request to the Ablatic API is authenticated with an API key. This page covers the key format, the two header schemes, and where keys come from.

Key format

A key looks like sk-ablatic- followed by 32 hex characters, 43 characters in total.

The key is shown once, at creation. The server stores only a SHA-256 hash of it, so it is never recoverable. If you lose a key, create a new one and revoke the old one.

Two header schemes

The same key works on both API surfaces with the same validation path. Use the header that matches the endpoint.

• OpenAI-style endpoints (for example POST /v1/chat/completions) read Authorization: Bearer sk-ablatic-....
• Anthropic-style endpoints (for example POST /v1/messages) read x-api-key: sk-ablatic-....

One key, both headers. Pick the header for the surface you are calling.

Where keys come from

Keys are created in the console.

Ablatic activates every account. To request access or become a customer, use the contact form on ablatic.ai or email [email protected]. Once we activate your account, you receive an email and a temporary password, and your first login forces a password change. Each account starts with one active key.

Endpoints that need no auth

Three endpoints are open and require no key:

• GET /v1/models
• GET /v1/messages/_health
• GET /health

Everything else requires a valid key.

Example

curl https://api.ablatic.ai/v1/chat/completions \
  -H "Authorization: Bearer sk-ablatic-..." \
  -H "Content-Type: application/json" \
  -d '{
    "model": "talos",
    "messages": [{"role": "user", "content": "Hello"}]
  }'

Next

• Models
• Console