Quickstart

1. Connect keys

Create a Strix API key in the dashboard (this is what clients send to Strix).
Store your OpenRouter key on Billing. Required for customer inference.

Keep keys in environment variables rather than source control.

export STRIX_API_KEY="your-strix-key"

2. Point a client at Strix

Base URL is always https://api.strixgate.dev/v1 (Claude Code uses ANTHROPIC_BASE_URL without the trailing /v1). Model: strix-auto or strix-coding.

Cursor

Settings → Models → Override OpenAI Base URL:

Base URL: https://api.strixgate.dev/v1/cursor
API key: your Strix key
Model: strix-auto

Claude Code

export ANTHROPIC_BASE_URL="https://api.strixgate.dev"
export ANTHROPIC_AUTH_TOKEN="$STRIX_API_KEY"

Claude Code calls POST /v1/messages on that host.

Codex

Add this to ~/.codex/config.toml, then export your Strix key before starting Codex:

model = "strix-auto"
model_provider = "strix"

[model_providers.strix]
name = "Strix"
base_url = "https://api.strixgate.dev/v1"
env_key = "STRIX_API_KEY"
wire_api = "responses"
http_headers = { "X-Strix-Client" = "codex" }

Codex calls POST /v1/responses. Strix translates that stateless Responses stream through the same routing, filtering, memory, savings, and usage pipeline as Chat Completions.

Other (OpenCode, Cline, Roo Code, Continue, Aider)

Same OpenAI-compatible /v1 values. Dashboard Setup has paste-ready config for each client. Do not rebuild IDE tools in the gateway — Strix forwards the tools the client owns.

Cursor-specific override path details: Cursor setup.

3. Make a request

curl https://api.strixgate.dev/v1/chat/completions \
  -H "Authorization: Bearer $STRIX_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "model": "strix-auto",
    "messages": [{"role": "user", "content": "Explain this failing test and suggest a fix."}],
    "max_tokens": 512
  }'

messages must be a non-empty array. A non-streaming response uses the familiar OpenAI chat-completion envelope. To force an intent lane, replace strix-auto with a model such as strix-coding, strix-deep, or strix-bug-hunt.

Memory is on by default. Facts appear in Dashboard → Memory; turn them off or forget them anytime. See memory.

4. Verify the route

Completion responses expose routing metadata through CORS-readable headers including x-strix-lane, x-strix-reason, x-strix-tier, x-strix-egress, and x-strix-request-id. Filter, routing, and cache savings evidence applies to every client. See routing evidence.

Quickstart

On this page