Loading the catalogue…
Loading the catalogue…
Same model, one lane, your call. Sovereign first, then European-hosted, then routed (typically non-EU). Default endpoint per lane is highlighted.
| Provider | Input / M | Output / M | Status |
|---|---|---|---|
AnthropicDefault | €13.80 | €69.00 | Active |
Stav speaks the Anthropic Messages API. Point the Anthropic SDK at base_url="https://api.stav.ai/v1" and your existing code keeps working — including cache_control markers and thinking mode, which pass through to Anthropic verbatim. Set STAV_API_KEY and the curl below works.
curl https://api.stav.ai/v1/messages \
-H "Authorization: Bearer $STAV_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"model": "claude-opus-4-1-20250805",
"max_tokens": 256,
"messages": [{"role": "user", "content": "Hello!"}]
}'Already using the OpenAI SDK? The same model is reachable at — drop in the slug above as the field and it works.
POST /v1/chat/completionsmodelSovereign-EU inference by default; the Smart Router lifecycle penalty drains traffic away from deprecating endpoints automatically. Add X-Stav-App-Id: <uuid> to attribute requests to a registered app.
Pick this model first.
Works — usually a fine pick.
Other models will serve you better.
Fit assertions set by the curator pipeline. 47 use cases mapped.
Model catalogue
Inference runs in US on anthropic. The model was created in US as well. Both training and inference fall under US compelled-disclosure regimes (CLOUD Act / FISA 702). Not appropriate for EU regulated-sector workloads without explicit legal sign-off.
Inference and (typically) training both happen under US jurisdiction — both CLOUD Act and FISA Section 702 reach. EU regulated-sector customers cannot use this combination for sensitive data without a derogation / case-by-case legal review.