generated: '2026-08-23'
method: probed
source: https://kateeva.com/wp-json/wp/v2/posts
limit_count: 0
note: >-
  Kateeva publishes no API documentation and therefore no rate limits. No RateLimit-*,
  X-RateLimit-* or Retry-After response header was observed on any of the roughly forty requests
  made during this pass, and no 429 was returned. This is a recorded absence, not an unchecked
  field: an agent consuming this surface gets no runtime throttling signal at all and must
  self-throttle, and any limit that does exist is enforced silently at the Apache origin with no
  advertised contract.
limits: []
response_headers: []
exhaustion_status: null
evidence:
- url: https://kateeva.com/wp-json/wp/v2/posts?per_page=2
  http_status: 200
  finding: 'Headers returned: content-type, x-robots-tag, access-control-expose-headers, access-control-allow-headers, access-control-allow-origin, vary, x-wp-total, x-wp-totalpages, link, allow, cache-control, server. No rate-limit header of any family.'
- url: https://kateeva.com/wp-json/
  http_status: 200
  finding: Root discovery document declares no rate-limit policy.
- url: https://kateeva.com/wp-json/wp/v2/posts?per_page=999
  http_status: 400
  finding: 'Bound enforcement exists on per_page (1..100) but it is a validation rule, not a rate limit; no Retry-After accompanies it.'