generated: '2026-09-12'
method: probed
source: >-
  Header inspection of live anonymous responses from https://websiteapi.agorareal.com/wp-json and a
  read of the full agorareal.com page sitemap (76 URLs) for a documented limit, 2026-09-12.
limit_count: 0
limits: []
response_headers: []
exhaustion_status: null
evidence:
- url: https://websiteapi.agorareal.com/wp-json/wp/v2/posts?per_page=1
  status: 200
  note: >-
    Response carries x-wp-total, x-wp-totalpages and a Link pagination header, but no X-RateLimit-*,
    no RateLimit-* and no Retry-After. Access-Control-Expose-Headers names only X-WP-Total,
    X-WP-TotalPages and Link, so no rate-limit header is even exposed to a browser client.
- url: https://websiteapi.agorareal.com/wp-json/agora/v1/get-categories
  status: 200
  note: Same — no rate-limit signal of any kind on the first-party agora/v1 namespace.
- url: https://agorareal.com/pricing/
  status: 200
  note: >-
    The published plan comparison lists API Access as a separately priced Enterprise add-on but
    states no call volume, quota or throttle for it.
note: >-
  Agora documents no rate limits anywhere on its public surface, and the one API it serves publicly
  emits no runtime rate-limit signal. An honest zero: an agent calling this API cannot tell how much
  it may call, and cannot learn from a response header either.