Unverified50% confidenceOpinionExact time
Most client SDKs or in-house message serializers keep only the OpenAI-standard content and tool_calls fields and discard the non-standard extension field reasoning_content, which is the structural reason the 400 error keeps recurring in projects such as opencode, LangChain and claude-code-router.
1
Sources
50%
Confidence
Long-term
Relevance
10/19/2026
First Seen
Sources
Related Entities
Related Claims
UnverifiedSwitching the same OpenAI Agents SDK Agent from the default Responses API to Chat Completions reduced format-error answers from 41 to 9, and switching to a public grounding system prompt reduced them to 20, indicating that API defaults are the main cause of format drift.73% similarUnverifiedLLM platforms such as OpenAI, Anthropic, Google, and Cohere each have independent API keys, request formats, and error codes, causing developers to incur substantial configuration burden in multi-model development.72% similarUnverifiedOpenAI-compatible interfaces usually cover only the core fields, and implementations of extended capabilities such as tools, response_format, and streaming events are not fully consistent across vendors; when encountering unsupported features, they may return a parameter error or silently ignore it.69% similarUnverifiedThe UI SDK provided by OpenAI lets developers validate the structure of message payloads at compile time, rather than only discovering missing fields or type errors at runtime.69% similarUnverifiedFunction Calling的核心痛点是缺乏统一标准，不同模型提供商（OpenAI、Anthropic、Google等）的接口和格式存在差异，导致工具集成代码无法跨平台复用69% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1067658API
curl https://kongchang.com/api/v1/knowledge/claims/1067658MCP
get_claim(id=1067658)