Look up any HTTP status code and get its official name, category (1xx-5xx), a plain-English description, and common usage notes. Agents use this to interpret API responses and decide on retry logic.
Note: The API expects the "code" field (integer). The demo sends "input" which may not match. For accurate results, use the CLI: delx http-codes 429
delx http-codes 429 delx http-codes 503 delx http-codes 201
curl -X POST https://api.delx.ai/api/v1/utils/http-codes \
-H "Content-Type: application/json" \
-d '{"code": 429}'{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": {
"name": "http-codes",
"arguments": { "code": 429 }
}
}The tool covers all standard IANA-registered HTTP status codes (100-599). Non-standard codes like 418 (I'm a teapot) and common vendor extensions (Cloudflare 520-530) are also included.
Currently one code per request. Batch multiple calls or use the CLI in a loop: for c in 200 301 404 429 503; do delx http-codes $c; done
Yes. For retryable codes (429, 500, 502, 503, 504), the response includes a "retryable" flag and suggested backoff strategy.