Loading the catalogue…
Loading the catalogue…
OpenAI's GPT-3.5 Turbo is a fast, text-only chat model built for high-volume, simple conversational tasks via the Chat Completions API, with tool calling and JSON mode support.
Overview. GPT-3.5 Turbo is OpenAI's chat-optimised text model, served through the Chat Completions API with a 16,385-token context window and a training cutoff in September 2021. It's a proprietary, closed-weight model built for straightforward conversational Inference rather than deep reasoning. Developers reach for it when they need a fast, well-established chat endpoint for everyday tasks without the overhead of a larger, newer model.
Key strengths. GPT-3.5 Turbo supports streaming responses, a distinct system-role prompt, tool calling, and JSON mode, making it straightforward to integrate into existing chat and automation pipelines. Its benchmark profile is modest — a coding_index of 10.7 and low overall quality signal — so its strength lies in dependable, low-complexity conversational handling rather than coding or multi-step reasoning. Parallel tool calls are available on newer snapshots, giving some flexibility for lightweight agentic patterns.
When to use it. Use GPT-3.5 Turbo for realtime, high-volume conversational workloads where the task is simple: FAQ-style chat, short-form completions, basic summarisation, or scripted assistant flows. It fits well as a Smart Router destination for simple-complexity requests that don't require deep domain reasoning or code generation. It is not the right choice when a task demands strong coding ability, multi-step reasoning, or up-to-date world knowledge.
Limitations. The model's training data ends in September 2021, so it has no awareness of more recent events or libraries. Its 16,385-token context window and 4,096-token max output are modest next to current-generation models, and it has no vision, audio, or document-understanding input support. It also lacks OpenAI's newer Structured Outputs JSON-schema response-format feature (limited to gpt-4o-mini and later) and shows weak coding and reasoning benchmark signals, so complex or code-heavy tasks are better routed elsewhere.
Sovereignty note. GPT-3.5 Turbo is built by OpenAI, a US-based company, so it operates under US jurisdiction, including CLOUD Act exposure. No EU data-residency or training-on-input guarantees are documented for this endpoint.
| Inference Provider | Sovereignty | Runs in | In / out per 1M | Status | Pin |
|---|---|---|---|---|---|
| L0 | €0.45 / 1.36 | Online |
17 use cases classified by the curator. The note says why.
Simple text classification tasks are within reach given tool-calling and JSON mode, suitable for high-volume low-complexity workloads.
Low-cost, high-volume conversational model with tool-calling and JSON mode; suitable for simple support flows but quality index of 3.2 limits complex ticket handling.
Legacy chat model is serviceable for straightforward email drafting tasks at low latency and cost.
JSON mode and tool-calling support structured entity extraction for simple documents within the 16k context window.
Native tool-calling support makes it usable for simple function-calling apps, but lacks the reasoning depth of newer generations for complex schemas.
Adequate for simple, low-stakes marketing copy generation given its conversational tuning, though creative quality lags newer families.
No code-specific benchmark evidence and quality index of 3.2 place this behind current code-tuned models for completion tasks.
Legacy general-purpose model without demonstrated code reasoning strength; better suited to simple explanations only.
16k context window constrains document Q&A over longer texts, and overall quality index trails newer generations.
16k context window and legacy architecture limit coherence and quality for extended long-form content versus newer generations.
16k context window limits handling of longer meeting transcripts, and quality index of 3.2 signals weaker synthesis versus current-gen models.
No sovereign deployment path (closed-weights, OpenAI-hosted) and CLOUD Act exposure make this unsuitable for regulated policy Q&A workloads requiring compliance rigor.
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.
curl https://api.stav.ai/v1/chat/completions \
-H "Authorization: Bearer $STAV_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"model": "openai/gpt-3.5-turbo",
"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