Do I need credentials for this example?

No. Public retrieval needs no account or API key. Send JSON to POST /api/v1/retrieve or use koskamo_retrieve through MCP.

Does the result explain every HTTP 429 response?

No. It identifies the registered code and its defining specification. Applications can add response details; read the specification and actual response before deciding how to retry.

What should my agent cite?

Keep the document title, dataset slug, document ID, document version, and source URL. Link the versioned Koskamo document and the original IANA source with the answer.

HTTP facts with citations.

Look up HTTP 429, inspect the returned evidence, and keep the defining source with the answer.

Connect your agent Explore knowledge

Scope the lookup

Set dataset to http-status-codes to search registered codes and their defining references. This narrows retrieval to the intended source; it does not make every returned passage relevant.

Follow the specification

The recorded 429 passage identifies Too Many Requests and RFC 6585. The registry entry is an index to the specification, not a complete guide to retry behavior. Follow the defining RFC for protocol requirements and inspect the actual server response.

Explore related registries

HTTP field names and system ports are separate datasets. Choose the registry that answers the question instead of assuming a status-code result defines a header or a service's behavior.

Try the lookup

Run this in a POSIX shell with curl. Public reads need no account or API key.

Lookup command

curl --fail-with-body 'https://koskamo.com/api/v1/retrieve' -H 'Content-Type: application/json' --data-raw '{"query":"429 Too Many Requests","dataset":"http-status-codes","top_k":3}'

Try in your browser Browse the dataset

Read the returned evidence

Selected fields from the first passage returned on 2026-10-04. This is a recorded example; current versions and ranking may change. A response can contain other matches, so check the title and text before using a passage.

Recorded passage

{
  "text": "HTTP 429 Too Many Requests is a 4xx client error status code in the IANA HTTP Status Code Registry.\n\n- Code: 429\n- Reason phrase: Too Many Requests\n- Class: 4xx (Client Error)\n- Defined in: RFC 6585",
  "datasetSlug": "http-status-codes",
  "datasetVersion": 65,
  "documentId": "fa2df016-31be-46c0-af42-9bdae9e95f49",
  "documentTitle": "429 Too Many Requests",
  "documentVersion": 1,
  "sourceUrl": "https://www.iana.org/assignments/http-status-codes/http-status-codes.xhtml"
}

Keep the citation with the answer

Keep documentId and documentVersion together with the dataset slug, document title, and original source URL. The dataset version describes the collection; it is not the document version. Preserve this evidence through summarization and show it with the final answer.

Versioned citation

429 Too Many Requests, document v1, http-status-codes. https://koskamo.com/data/datasets/http-status-codes/documents/fa2df016-31be-46c0-af42-9bdae9e95f49?version=1 Source: https://www.iana.org/assignments/http-status-codes/http-status-codes.xhtml

Read the cited version Read the original source

An empty passages array means there is no returned evidence to cite. An HTTP error is a failed lookup, not an empty result. On 429, respect Retry-After; on other failures, report the failure instead of inventing a source.

Frequently asked questions

Do I need credentials for this example?: No. Public retrieval needs no account or API key. Send JSON to POST /api/v1/retrieve or use koskamo_retrieve through MCP.
Does the result explain every HTTP 429 response?: No. It identifies the registered code and its defining specification. Applications can add response details; read the specification and actual response before deciding how to retry.
What should my agent cite?: Keep the document title, dataset slug, document ID, document version, and source URL. Link the versioned Koskamo document and the original IANA source with the answer.