Skip to content
anythingai.space
Backend for AIbeginner10 min · 10 steps

HTTP and Status Codes

Status codes are standard outcome signals; a client that reacts to each one correctly survives the 429s, 5xx and timeouts every LLM integration hits.

POST /chatWHAT COMES BACK ON A BAD DAY429 Too Many Requests503 Unavailable504 Gateway Timeoutread timeoutAssistant APIHTTP clientModel APIprimary region429 · 503
requesterrorresponsetokendataheavy work
1 / 10
ProblemStep 1 of 10

Most LLM incidents are 429s, 5xx and timeouts

An AI backend makes HTTP calls all day: to the model provider, the vector store, the ticketing system. When those calls fail, they fail with a status code or a timeout.

A client that treats every failure the same way either gives up on errors that would have healed in a second, or keeps hammering a request that can never succeed.

Watch outRetrying a 400 forever and giving up on a 429 are the same bug: ignoring what the server told you.

Lesson 2 of 20 in Backend for AI