specification: API Commons Rate Limits
specificationVersion: '0.1'
schema: https://raw.githubusercontent.com/api-evangelist/interface-research/main/schema/api-commons.yml#/$defs/RateLimits
provider: APA Corporation
providerId: apa
generated: '2026-09-14'
method: probed
source: response headers observed live on https://apacorp.com/wp-json across ~60 requests on 2026-09-14
created: '2026-05-04'
modified: '2026-09-14'
tags:
  - Oil And Gas
  - Energy
  - Exploration
  - Production
  - Rate Limiting
description: >-
  APA Corporation publishes no rate limits for its REST surface and returns no rate-limit signal on
  the wire. This is a measured zero, not an unchecked gap: roughly sixty requests were made across
  eleven route groups on 2026-09-14 and no X-RateLimit-*, RateLimit-* or Retry-After header appeared
  on any response, and no 429 was ever returned. REPLACES A SCAFFOLD: until 2026-09-14 this file
  carried invented per-tier limits (10/100/1000 requests per minute across Free, Professional and
  Enterprise tiers, with a full X-RateLimit-* header set) written by the 2026-05-04 bulk sweep and
  never observed. None of it was real. It has been removed.
limit_count: 0
limits: []
headers:
  limit: null
  remaining: null
  reset: null
  retryAfter: null
  policy: null
headers_observed: []
responseCodes:
  throttled: null
  quotaExceeded: null
observed_behaviour:
  requests_made: ~60
  window: single session, 2026-09-14
  throttled_responses: 0
  note: >-
    The surface sits behind Cloudflare in front of WP Engine, both of which apply unpublished edge
    protections, so a limit almost certainly exists — it is simply not documented and not signalled.
    An agent calling this API has no runtime way to learn how much budget it has left, and would
    discover a limit only by being cut off.
caching_as_the_real_control:
  note: >-
    What the surface does signal is cacheability: Cache-Control "max-age=600, must-revalidate" with
    CF-Cache-Status and Age on every documented route. A well-behaved client that honours it will
    generate very little origin load, which is plausibly why no explicit limit was ever needed.
evidence:
  - url: https://apacorp.com/wp-json/apa-ticker/v1/quote
    status: 200
    note: 'Headers returned: cache-control, x-cacheable, cf-cache-status, age, x-cache. No rate-limit family header.'
  - url: https://apacorp.com/wp-json/wp/v2/posts?per_page=1
    status: 200
    note: 'Headers returned: x-wp-total, x-wp-totalpages, link, cache-control. No rate-limit family header.'
checked: '2026-09-14'
maintainers:
  - FN: Kin Lane
    email: kin@apievangelist.com