PixCode documentation

One base URL, two protocols. Change one variable and your coding agent is connected.

Quickstart

Get a key from the console first, then wire it into whichever tool you already use.

By tool

Pick the one you use and copy it across. Anything not listed works too, as long as it takes a custom endpoint.

export ANTHROPIC_BASE_URL="https://api.pixcode.ai/anthropic"
export ANTHROPIC_AUTH_TOKEN="sk-px-..."
export ANTHROPIC_DEFAULT_OPUS_MODEL="pixcode-max"
export ANTHROPIC_DEFAULT_SONNET_MODEL="pixcode-pro"
export ANTHROPIC_DEFAULT_HAIKU_MODEL="pixcode-fast"
export API_TIMEOUT_MS=3000000

claude

Endpoints & auth

There are only two endpoints. Auth accepts both x-api-key and Authorization: Bearer — use whichever your tool sends. The gateway egresses from Singapore, one less hop to upstream.

curl https://api.pixcode.ai/anthropic/v1/messages \
  -H "x-api-key: sk-px-..." \
  -H "anthropic-version: 2023-06-01" \
  -H "content-type: application/json" \
  -d '{
    "model": "pixcode-pro",
    "max_tokens": 1024,
    "messages": [{ "role": "user", "content": "hi" }]
  }'

Model aliases

All three aliases carry 1M context; pick by task length. Assign them by role in your agent config: titles and compaction to the cheap one, the run that has to land to the strong one.

The official names and per-line rates for all 31 models are on the models page. The aliases are just three defaults.

Limits & errors

The concurrency cap stops a few always-on scripts from eating the upstream capacity. When you hit it you get a retry-after — wait for the in-flight requests. A single request is also hard-capped at 780 seconds on the gateway, however generous your client timeout.