Unverified50% confidenceDecision RuleExact time
Production routing logic should not look only at the HTTP status code, but should also check whether finish_reason and content are non-empty, and treat finish_reason of length with empty content as a hard failure rather than a parseable result.
1
Sources
50%
Confidence
Long-term
Relevance
10/16/2026
First Seen
Sources
Related Entities
Related Claims
UnverifiedWhen the subject of a check is LLM-generated text, the reasons for a check passing or failing are not written in the code but depend on factors such as model output and prompt constraints that cannot be exhaustively determined through static reading.64% similarUnverifiedWhen large language model APIs return responses, they typically include a finish_reason field with common values including stop, length, and tool_calls.61% similarUnverifiedIn HTTP semantics, a missing field is not equivalent to an empty field, and many APIs perform strict validation on empty strings.60% similarUnverifiedFormat compliance and semantic correctness in code large models are two relatively independent capability dimensions, and when selecting a model one cannot look only at pass rates like HumanEval; an end-to-end applicability evaluation for the actual output channel is also needed.60% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1047907API
curl https://kongchang.com/api/v1/knowledge/claims/1047907MCP
get_claim(id=1047907)