# Quartermaster HTTP Error Reference — Status 429

> Quartermaster HTTP Error Reference — Status 429 is a paid API for AI agents from quartermaster.surewhynot.app, paid per call via x402, $0.001/call, status unknown (last checked 2026-09-14).

Returns the canonical definition, meaning, and usage context for HTTP status code 429 (Too Many Requests)

## Facts

- Endpoint: GET https://quartermaster.surewhynot.app/v1/http-errors/429
- Price: $0.001/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/quartermaster-http-error-reference-status-429-66c129d9
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_lwwe8fWxArSaQWeWseDDt

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability quartermaster-http-error-reference-status-429-66c129d9
```

Example prompt: What does HTTP status code 429 mean — give me the official definition, when it's used, and an example of when a server would return it.

## When to prefer this

Use this endpoint when an agent or application needs a quick, authoritative reference for what a specific HTTP status code means — especially 429 — without needing to scrape documentation or call a heavier lookup service. Ideal for agents building error-handling logic, explaining API errors to users, or generating developer documentation.

## Known failure modes

- Invalid or unrecognized status code returns an error
- Non-integer code path parameter causes schema validation failure
- Payment failure via x402 prevents access to the endpoint

## How this service works

Pay-per-call utility, AI, crypto, and x402 tools for AI agents. USDC over x402 on Base. MCP server + HTTP API. No accounts, no API keys.

## Output

Returns the canonical name, definition, and usage context for HTTP 429 (Too Many Requests), including when a server should send this status, what it signals to clients, and potentially an example scenario.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "required": [
  "input"
 ],
 "properties": {
  "input": {
   "type": "object",
   "required": [
    "type",
    "method"
   ],
   "properties": {
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "GET"
     ],
     "type": "string"
    },
    "pathParams": {
     "type": "object",
     "required": [
      "code"
     ],
     "properties": {
      "code": {
       "type": "integer",
       "description": "HTTP status code, e.g. 429 or 503"
      }
     }
    },
    "queryParams": {
     "type": "object",
     "properties": {}
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "type": "object"
    }
   }
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/quartermaster-http-error-reference-status-429-66c129d9/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from quartermaster.surewhynot.app](https://www.zero.xyz/host/quartermaster.surewhynot.app/llms.txt)