メインコンテンツへスキップ
更新日: 2026-06-06

Reasoning Models

This page only documents reasoning behavior that was revalidated against Crazyrouter production on 2026-03-22. For OpenAI-compatible integrations, the current guidance is:
  • If you only want stronger reasoning and only need the final answer, use Chat Completions with reasoning_effort
  • If you need a stable, inspectable reasoning output, prefer the Responses API and see GPT-5 Thinking Mode

Verified combinations


Chat Completions: reasoning_effort

The following request shape currently works in production:
cURL
Available reasoning_effort values:

Current response behavior

In the 2026-03-22 production recheck:
  • the request succeeded
  • the final answer was returned in message.content
  • message.reasoning_content did not reliably contain usable content
So if you only want stronger reasoning, Chat Completions with reasoning_effort is still usable. If you need a visible reasoning summary field, do not treat Chat Completions as the primary path.

When you need inspectable reasoning output

The more reliable production path is the Responses API:
cURL
Verified output.type values:
For concrete response shapes, summary fields, and streaming event names, see:

Current recommendation

  • For new builds that need to log or display reasoning summaries, start with the Responses API
  • For existing Chat Completions integrations that only care about the final answer, reasoning_effort is still a valid path
  • Do not assume all OpenAI-compatible reasoning models will reliably expose reasoning_content
Reasoning requests usually increase both latency and token usage. Higher reasoning_effort generally costs more.