Loading the catalogue…
Loading the catalogue…
OpenAI's compact closed GPT-5.4 model for text and image input, with configurable reasoning effort and a 400,000-token context.
| Inference Provider | Sovereignty | Runs in | In / out per 1M | Status | Pin |
|---|---|---|---|---|---|
| L0 | €0.18 / 1.13+2 rates | Online |
10 use cases classified by the curator. The note says why.
Nano-tier variant positioned for high-volume, low-latency inference, which suits bulk classification where per-call cost and throughput dominate. Capability data is not curated, so the call rests on size-class positioning rather than a published benchmark.
Nano-tier latency suits high-volume first-line support replies on simple queries. Escalation and multi-turn reasoning quality are not documented, and OpenAI's US-jurisdiction exposure applies to customer data routing.
Suitable for straightforward named-entity pulls at scale given the nano-tier cost and latency profile. Recall on domain-specific entities is not documented.
Short-form summarisation of transcripts is within the nano-tier's expected range. Long meeting transcripts may exceed a context window that is not published.
Nano-tier model can handle schema-bound extraction from short, well-formed inputs. Complex or long-document extraction is not supported by any published context window or benchmark.
Adequate for short-to-medium summarisation where speed and cost matter more than depth. Context window is unspecified, so long-input summarisation cannot be confirmed.
Nano-tier size class is suited to lightweight, high-volume tagging workloads where label accuracy needs are modest. No published accuracy figures are available to confirm performance against larger variants.
Nano-tier size class generally trades multi-step reasoning depth for speed, which works against multi-file agentic coding loops. No coding benchmark or tool-use capability is documented to offset this.
Closed-weights model under US CLOUD Act jurisdiction, which is a poor match for compliance-driven redaction of sensitive data. Redaction recall is also not documented for a nano-tier variant.
Sourced numbers, not our own evaluations. Percentiles are against the whole Stav catalogue.
Computed from aa-intelligence-index, gpqa-diamond, aa-engineering-index, aa-coding-index, livecodebench, terminal-bench-v4, ifbench, aa-lcr.
curl https://api.stav.ai/v1/chat/completions \
-H "Authorization: Bearer $STAV_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"model": "openai/gpt-5.4-nano-2026-03-17",
"messages": [{"role": "user", "content": "Hello!"}]
}'→ X-Stav-Request-Id · X-Stav-Model · X-Stav-Provider → X-Stav-Sovereignty-Level — the rung the request was served at