Authentication

Every endpoint uses the same credential: an API Key created in the console, sent with each request in the Authorization header. There is no other authentication method and no per-endpoint rules.

One header

Authorization: Bearer {key}

One Key works across every prefix. Keys are created, rotated, and revoked at Console → API Keys; revocation takes effect immediately.

Where each SDK puts the Key

You don't assemble the header yourself — the official SDKs do it; we also accept the header names those SDKs send by default.

Try one

curl https://api.deepraxis.com/model/v1/models \
  -H "Authorization: Bearer $PRAXIS_API_KEY"

What an auth failure looks like

A missing, invalid, or revoked Key returns 401, with a body in the format of that prefix (see Errors). Never retry a 401 — fix the Key and send again.

Safekeeping

• Use it server-side only; never ship it in a browser, mobile app, or public repository.
• Use an environment variable (PRAXIS_API_KEY in the examples), not code.
• If you suspect a leak, revoke it in the console and create a new one; the old Key stops working immediately.