API reference

Authentication

Proxy traffic uses a Shield virtual key: Authorization: Bearer sk-andora-…

Management APIs (keys, budgets, kill switch) use a dashboard session or a workspace API token (andora_pat_…) from Settings → Security.

See the quickstart to create your first virtual key.

Proxy — chat completions

OpenAI-compatible body. Provider is required in the path.

POST https://useandora.com/proxy/{provider}/v1/chat/completions
Authorization: Bearer sk-andora-...
Content-Type: application/json

{
  "model": "gpt-4o-mini",
  "messages": [{"role": "user", "content": "Hello"}]
}

Providers: openai, anthropic, gemini, groq, mistral, openrouter, deepseek, and others listed in Docs. Bedrock and Vertex are beta (endpoint + Bearer).

curl example

curl -s "https://useandora.com/proxy/openai/v1/chat/completions" \
  -H "Authorization: Bearer $ANDORA_VIRTUAL_KEY" \
  -H "Content-Type: application/json" \
  -d '{"model":"gpt-4o-mini","messages":[{"role":"user","content":"Hello"}]}'

Management (PAT)

Create tokens in the dashboard. Example workspace kill switch:

curl -X POST "https://useandora.com/api/v1/workspace/kill-switch" \
  -H "Authorization: Bearer $ANDORA_PAT"

Core concepts

• Virtual keys — customer-facing keys with spend limits; hashed at rest.
• Budgets — hard caps per key/workspace; mid-stream cutoff on streams.
• Failover — Control+ can reroute on provider errors and rate limits.
• Guardrails — policy templates for token ceilings and agent loops.