operational·41 regions

One endpoint.
Every model worth using.

Skidder fronts the heavy hitters behind a single key, one billing ledger and sliding-window limits you actually understand. Swap models by editing one string.

Get your key How it works

skidder · /v1/chat200 OK

curl https://api.skidder.wtf/v1/chat/completions \
  -H "Authorization: Bearer $SKIDDER_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "model": "claude-sonnet-5",
    "stream": true,
    "messages": [{"role": "user", "content": "ship it"}]
  }'

Req / min

320

Tier-1 pool

p50 latency

41ms

Uptime 30d

99.98%

live traffic · last 60s

claude-sonnet-51.4k t/s

gpt-6.1-sol980 t/s

gemini-3.1-pro760 t/s

grok-4.20410 t/s

kimi-k3240 t/s

everything in the pool

Claude Opus 5.1Claude Sonnet 5Claude Haiku 4.5GPT-6.1 SolGPT-6.1 TerraGPT-6.1 LunaGPT-5.5 CodexGemini 3.1 ProGemini 3.1 FlashGrok 4.20Grok 4.6Kimi K3Qwen 3.8 MaxGLM 5.2DeepSeek V4 ProLlama 4 405BMistral Large 3Nemotron 3 Super

why bother

Built for agents that
never stop running.

Long-lived agents do not tolerate provider churn. Upstream goes down, rate limits move, a model is deprecated mid-run. Skidder absorbs that so your process keeps its footing and keeps its keys.

Drop-in OpenAI shape

Streaming, tool calls, JSON mode and vision work the same on every model. Nothing to rewrite.

Real sliding windows

Rate limits count over a rolling interval, so bursts land where you expect instead of at the reset.

Per-key ceilings

Spend and RPM caps live on the key. A runaway loop kills itself, not your month.

One ledger

Every model, every key, one export. Reconcile in a spreadsheet or pipe it into your own stack.

failover.loghealthy