generated: '2026-08-12'
method: probed
source: https://energyx.com/wp-json/wp/v2/posts
limit_count: 0
limits: []
response_headers: []
exhaustion_status: null
note: >-
  EnergyX 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 seventy 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 WordPress host or CDN
  with no advertised contract. The one hard bound the server does publish is not a rate limit but a
  page-size cap — per_page is validated to 1..100 and returns 400 rest_invalid_param above it —
  which matters most on the 2,639-record media collection.
evidence:
- url: https://energyx.com/wp-json/wp/v2/posts?per_page=2
  http_status: 200
  finding: No rate-limit header of any family present in the response.
- url: https://energyx.com/wp-json/wp/v2/posts?per_page=999
  http_status: 400
  finding: 'per_page cap is 100, enforced as a validation error rather than a throttle.'