Enable extended reasoning on eligible models by appending the :thinking suffix.
Not yet available.
Some models support an extended internal reasoning phase — a "thinking" step where the model works through the problem before producing its final answer. Append :thinking to an eligible model slug to activate this mode. The model's reasoning trace is returned alongside the answer, and accuracy on complex tasks improves significantly.
When :thinking is active, the response includes an additional thinking field in the message object alongside the standard content:
The thinking field contains the model's internal reasoning steps in plain text. The usage object includes a thinking_tokens count — these are billed separately (see Pricing below).
When "stream": true is set, thinking tokens stream in a separate thinking delta field before the content deltas begin:
The :thinking variant is most valuable for:
For simple queries, thinking adds latency and cost without much benefit. Use the standard variant for conversational or lookup tasks.
Thinking tokens are billed at the model's thinking token rate, which may differ from the standard output token rate. Check the model catalog at GET /api/models/{slug} for the exact DA per million thinking tokens. A typical thinking trace is 300–1000 tokens per request.
The thinking field in the response message is an extension — the OpenAI SDK will ignore it unless you access the raw response. Use .model_dump() in Python or inspect the raw JSON in Node.
Note. Not all models support the
:thinkingvariant. Check the catalog — models withcapability: reasoningsupport it. Applying:thinkingto an ineligible model returns a404 model_not_founderror.