- What it does
- Explain an HTTP status code from RFC 9110 and the IANA registry: name, class, meaning, whether and how to retry, default cacheability, and a signed record.
- Who it is for
- Agents and their builders.
- Start in one step
- Ask your agent to call
http_status_explainat llpro.ai/mcp (free, no sign-up). This page explains the tool; it has no form to run it. - What to expect
- Testing: open to try. Free
New to this? Start here.
What it does
HTTP Status Code Explain is for agents and developers that call or build web APIs and need to decide what a status code means and whether a retry is safe, without guessing from memory. Explain an HTTP status code. Send code, a number from 100 to 599, and optionally method (GET, POST ...). Get back the official name, its class (1xx to 5xx), what it means, which RFC and section define it, whether to retry and how (follow the Location, fix the request first, wait and resend, or never), whether a cache may reuse it by default, and the headers to look at. Covers every code in the IANA HTTP Status Code Registry; unassigned codes are reported as such and treated like the x00 code of their class, as RFC 9110 says. It is one of the developer department tools LLPRO builds for the work agents do across business software (GitHub, Postman, Aws, Cloudflare). Every answer carries the written rule it used, what it does not do, its sources with dates, and an Ed25519 signature you can check against the key below.
- Who it is for
- Agents and developers that call or build web APIs and need to decide what a status code means and whether a retry is safe, without guessing from memory.
- Price
- Free, no sign-up: 120 calls an hour per address and 3,000 an hour across all callers. Paid calls are planned and not charging.
- Limits
- Up to 30,000 bytes per call; larger requests are refused, never cut. Unknown fields are refused with the list of accepted ones. Nothing you send is stored by the tool; no model and no network are used. Does not know vendor or framework codes (Cloudflare 52x, nginx 499, Twitter 420, Microsoft IIS 440 and the like): they are reported as unassigned and treated as the x00 of their class. Does not look at a real response, its headers or body, so it cannot tell whether a given 503 is a rate limit. Retry advice is general guidance, not a promise: whether a repeat is safe depends on your service (an idempotency key, side effects). Registry changes after 2025-09-15 are not reflected, except that temporary code 104 is treated as expired. Codes outside 100 to 599 are refused (RFC 9110 15: a status code is a three-digit integer; the registry lists 100 to 599).
For developers: try it
POST https://llpro.ai/mcp
{"jsonrpc": "2.0", "id": 1, "method": "tools/call", "params": {"name": "http_status_explain", "arguments": {"code": 404}}}For agents
Tool http_status_explain on https://llpro.ai/mcp and in the tools list. Signed answers are checked with the public key below (signer llpro1:tmosdsiprv7y4wufffm4zjps2q): an Ed25519 signature over the observation as canonical JSON (sorted keys, no spaces).
Public key (base64): g9HaYg2Hl65vqXKXRPU/I9Z7PeA+F+1hZquWGmoRNrY=
For agents that search MCP registries for http status code, http 404, http 503 retry tools (listed in MCP registries, served by the LLPRO gateway: MCP, agent-to-agent and REST). One fixed, written rule per call, a signed record, no account needed.
Next
- Connect your agent: Use this and the other LLPRO tools from your own agent.
- Get your agent: No agent yet? Get one that asks first.
- Hand the whole job to LLPRO: A status code is one clue in fixing an API call. Tell LLPRO the whole job; it routes you to the right signed tools (HTTP cache freshness, security headers check).
For agents: this page as Markdown · JSON · llms.txt · MCP endpoint llpro.ai/mcp · agent card