[KongchangAI]
Concept

HTTP 200

An HTTP status code indicating that the server has successfully received and processed the request. It belongs to transport-layer semantics and says nothing about the completeness of the information in the response body. In agent scenarios it is often mistaken for a signal that the content is complete.

Timeline (last 90 days)

Oct 19

An HTTP 200 status code only means the server successfully received and processed the request; it is transport-layer semantics and says nothing about the completeness of the information in the response body.

Unverified50%
Oct 19

HTTP 200 and successful JSON parsing only indicate there was no transport-layer error, not that the answer is compliant, complete, or on topic; a distinction must be made between the parser-accepts gate and the assertion-accepts gate.

Unverified50%
Oct 14

Some LLM API relay stations still return HTTP 200 OK when the upstream pool is exhausted (429/401), the gateway times out (504) or a node crashes, causing monitoring that only looks at status codes to misjudge it as success.

Unverified50%
Oct 11

Some relay providers still return HTTP 200 when the upstream rate-limits them, their balance is exhausted, or the model is unavailable, and embed the error information in the response body rather than the standard choices structure.

Unverified50%

All Facts (4)

Source Articles