generated: '2026-09-05'
method: probed
source: >-
  Live anonymous requests and response-header inspection against
  https://www.parentcenterhub.org/wp-json/ on 2026-09-05, plus
  https://www.parentcenterhub.org/robots.txt. CPIR publishes no developer documentation, so there
  is no documented limit to quote.
limit_count: 0
detail: >-
  No API rate limit is published and none was observed. A full inspection of the response headers on
  /wp-json/cn-api/v1/entry returned no `X-RateLimit-*`, no `RateLimit-*` and no `Retry-After`
  header. Paging the directory collection eight times at per_page=100 in quick succession on
  2026-09-05 completed without throttling, a 429, or any degradation.
response_headers: []
exhaustion_status: null
advisory_signals:
  - source: https://www.parentcenterhub.org/robots.txt
    status: 200
    directive: 'Crawl-delay: 600'
    detail: >-
      The Yoast-generated robots.txt sets a `Crawl-delay: 600` for all user-agents — ten minutes
      between requests. This is the ONLY throttling signal CPIR publishes anywhere. It is crawler
      guidance rather than an enforced API limit, and it is not returned on any API response, but it
      is a clear statement of the request rate the operator considers acceptable and an integrator
      should respect it rather than page the directory aggressively.
observed_headers_on_api_response:
  - 'content-type: application/json; charset=UTF-8'
  - 'access-control-allow-headers: Authorization, X-WP-Nonce, Content-Disposition, Content-MD5, Content-Type'
  - 'access-control-expose-headers: X-WP-Total, X-WP-TotalPages, Link'
  - 'allow: GET'
  - 'link: <https://www.parentcenterhub.org/wp-json/>; rel="https://api.w.org/"'
note: >-
  `allow: GET` on the directory collection is the clearest runtime statement the API makes about an
  anonymous caller: reads only.