# HTTP status code lookup

Look up an HTTP status code or search by words: meaning, typical cause and whether to retry.

- Endpoint: `POST https://setget.net/v1/tools/http-status` with JSON `{"input": {...}}`
- MCP: `run_tool` with `slug` = `http-status`
- Page: https://setget.net/tools/http-status

## Inputs

- `query` (required, string): A status code such as 404, or words to search for such as "too many requests".

## Example 1

```json
{"input":{"query":"429"}}
```

Result:

```json
{"query":"429","count":1,"matches":[{"code":429,"name":"Too Many Requests","class":"client error","official":true,"meaning":"The client has sent too many requests in a given time.","cause":"A rate limit was hit; the Retry-After header often says how long to wait.","retry":true}]}
```

## Example 2: Search by a word

```json
{"input":{"query":"teapot"}}
```

Result:

```json
{"query":"teapot","count":1,"matches":[{"code":418,"name":"I'm a teapot","class":"client error","official":false,"meaning":"A joke code from an April Fools specification; some sites use it to refuse automated requests.","cause":"An Easter egg, or a server that blocks bots with it.","retry":false}]}
```

**What does "official" mean?** Official codes are in the IANA registry. The others are in real use by nginx, Cloudflare and some frameworks but are not standardised.

**What does "retry" tell me?** Whether sending the same request again, after a pause, has a fair chance of working. For most 4xx codes you must change the request first.
