← Agent Data Hub · Search endpoints · /llms.txt

HTTP Status Code Complete Diagnostic & RFC Specification Oracle

Explains any HTTP status code (100–599), whether it is retryable by an AI agent, RFC specification, and resolution strategy.

Call it (no API key)

GET https://api.agentdatahub.de/api/v1/call/dev-http-status-oracle?code=402&compact=1

Full metadata: without compact=1 · Markdown: format=llm · Only some fields: add &fields=a,b.c · MCP: tool call_api with {"apiId":"dev-http-status-oracle"}

Parameters

codeHTTP status code e.g. 402, 429, 503, 418 (default: 402)

Example response (live, compact)

{
  "apiId": "dev-http-status-oracle",
  "data_freshness": "cached",
  "data": {
    "status_code": 402,
    "class": "4xx",
    "phrase": "Payment Required (x402)",
    "retryable": true,
    "action": "Sign x402 USDC payment payload and retry with X-PAYMENT header."
  },
  "source": "IETF RFC 9110 + x402 Protocol Specification",
  "license": "100% Platform Owned Reference"
}

Source & license

SourceIETF RFC 9110 + x402 Protocol Specification
License100% Platform Owned Reference
Source URLhttps://www.rfc-editor.org/rfc/rfc9110
Termshttps://localhost:3000/llms.txt
CategoryDeveloper, Tech & Web › 3. DNS, Network & Domain Intelligence