generated: '2026-09-09'
method: probed
source: >-
  GET https://www.countrycalling.codes/api/capabilities (200, 2026-09-09) — the
  provider publishes its limits machine-readably in result.limits; cross-checked
  against the OpenAPI 429/413 response definitions.
limit_count: 0
policy: >-
  "No application-level per-client quota. Hosting may enforce limits; clients
  should handle 429 and Retry-After when provided." (verbatim from
  /api/capabilities result.limits.rateLimit)
limits: []
request_size_limits:
  - scope: per-request
    kind: body-size
    limit: 65536 bytes (413 on excess)
  - scope: per-request
    kind: batch-items
    limit: 100 phone numbers per batch normalization call
  - scope: per-request
    kind: input-length
    limit: 64 characters per phone number
  - scope: per-request
    kind: scheduling-range
    limit: 31 days / 8 participants for calling-window queries
headers:
  exhaustion_status: 429
  retry: Retry-After (when the hosting platform enforces a limit)
  rate_limit_headers: none  # no X-RateLimit-*/RateLimit-* headers observed on live responses
notes: >-
  An honest zero on quotas: the provider deliberately publishes no per-client rate
  limit, and none was observed on live anonymous calls. The only throttling an agent
  can encounter is hosting-level (Vercel/Cloudflare) 429s, which the OpenAPI documents
  with Retry-After guidance.