generated: '2026-09-05'
method: searched
source: https://www.ceps.eu/
limit_count: 0
limits: []
response_headers: []
exhaustion_status: null
note: >-
  CEPS publishes no API and therefore no rate limits. This file previously held a five-row
  scaffold written by the 2026-05-04 bulk sweep — 10/100/1000 requests per minute by tier, a
  full X-RateLimit-Limit / X-RateLimit-Remaining / X-RateLimit-Reset / Retry-After /
  RateLimit-Policy header set, and 429/503 exhaustion codes — none of which CEPS has ever
  published or served. It is replaced here by the measured zero. What the site actually enforces
  on automated clients is a Cloudflare managed challenge (HTTP 403 with a "Just a moment..."
  interstitial, ~5.7 KB), which fires unpredictably across ceps.eu paths and on every ceps.eu
  subdomain root; that is bot mitigation, not a documented, header-signalled rate limit, and is
  deliberately not recorded as one.
searched:
  - url: https://www.ceps.eu/
    status: 200
    result: no developer or API documentation of any kind, so no limits section to read
  - url: https://www.ceps.eu/robots.txt
    status: 200
    result: >-
      crawl directives only (Disallow /wp-json/, /feed/, /*/feed/, /wp-admin/, /?s=); no
      Crawl-delay and no rate guidance
observed_edge_behaviour:
  mechanism: Cloudflare managed challenge
  observed_status: 403
  observed_body_bytes: ~5700
  is_documented_rate_limit: false
  note: >-
    Recorded as context, not as a limit. Per the pipeline's own rule a bot challenge is not a
    dead page and is not a published quota.
maintainers:
  - FN: Kin Lane
    email: kin@apievangelist.com