Unverified50% confidenceFactExact time
In HTTP API integrations, because response bodies are dynamic JSON and HTTP status codes only reflect transport-layer success, schema drift is easily masked.
1
Sources
50%
Confidence
Long-term
Relevance
11/3/2026
First Seen
Sources
Related Entities
Related Claims
UnverifiedOnce the status line and headers of an HTTP streaming response have been sent, at the protocol level errors can no longer be expressed through status codes, and errors must be explicitly encoded as in-stream events (such as agreeing on an error field within JSON deltas).74% similarUnverifiedEven when using structured output interfaces, occasional format drift or missing fields from the model still occur, and production environments typically require adding JSON validation and exception fallback mechanisms.72% similarUnverified大语言模型的API接口（如OpenAI的Chat Completions API、Anthropic的Messages API）通常采用HTTP REST协议，返回JSON格式数据，并支持Server-Sent Events流式输出71% similarUnverifiedMost agent frameworks, when parsing tool responses, only check whether the transport layer succeeded (HTTP 200, JSON parseable), and do not verify whether the content semantics match expectations.70% similarUnverifiedResponse transformation plugins can be configured on API gateways such as Kong and Nginx to remove sensitive fields at the traffic layer via JSON Path rules.70% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1132933API
curl https://kongchang.com/api/v1/knowledge/claims/1132933MCP
get_claim(id=1132933)