want_message_cap_reached

HTTP 429

POST /v1/wants refused a message because this source has already left 5 in the last 24 hours. This is a cap on what is stored, not the per-minute rate_limited brake, and nothing was stored. The Retry-After is an upper bound: a slot frees as the oldest message passes 24 hours.

Response shape

{
  "type": "https://cogdepot.com/problems/want_message_cap_reached",
  "title": "<short human-readable summary>",
  "status": 429,
  "detail": "<what happened on this occurrence>",
  "reason": "want_message_cap_reached",
  "retryAfterSeconds": "<seconds until the window rolls>"
}

Branch on reason. The title is prose and may be reworded; reason is the stable contract. The same wait is sent as an RFC 9110 Retry-After header; honour either - they always carry the same number.