Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.raziel.fun/llms.txt

Use this file to discover all available pages before exploring further.

Every request to the Raziel gateway needs an API key. Keys take the form rz_live_xxxxxxxxxxxx and act as the single credential for all gateway endpoints — Anthropic-compatible and OpenAI-compatible alike.
Your key is shown exactly once at issue time. Copy it before you close or navigate away — it cannot be retrieved afterwards.

​
Issue a key

1

Open the API keys page

Sign in, then navigate to Customer → API Keys.
2

Add a label (optional)

Labels help you tell keys apart later. Use descriptive names like laptop, ci, or side-project. The label has no effect on authentication.
3

Click Issue key

The full key is displayed immediately in the dashboard. Copy it now and store it somewhere safe.

​
Use the key

Pass the key as a Bearer token in the Authorization header on every request: 
curl https://raziel.fun/gateway/v1/messages \
  -H "Authorization: Bearer rz_live_xxxxxxxxxxxx" \
  -H "Content-Type: application/json" \
  -d '{"model":"claude-sonnet-4-6","max_tokens":256,"messages":[{"role":"user","content":"Hello"}]}'
If you set up the CLI, your key is saved automatically to ~/.config/raziel/config.json and injected by the proxy — you do not need to pass it manually when using razi claude.

​
Revoke a key

Go to Customer → API Keys, find the key row, and click revoke. Revocation takes effect immediately — any in-flight request using that key will fail with a 401 auth_error.

​
Use multiple keys

You can issue as many keys as you need. Label each one for its intended context so you can revoke a single surface (e.g., a compromised CI secret) without rotating everything else.
The CLI setup command (npx @raziel.fun/cli setup) opens a browser sign-in flow and saves your key automatically to ~/.config/raziel/config.json. Run it once per machine and you are done.