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: Dredd
providerId: dredd
created: '2026-05-04'
modified: '2026-09-13'
generated: '2026-09-13'
method: searched
source: https://dredd.org/en/latest/usage-cli/
limit_count: 0
description: >-
  Dredd serves no HTTP API, so it publishes no rate limits, returns no
  rate-limit response headers and has no throttled status code. An honest zero,
  measured 2026-09-13 against the full published documentation.
headers: {}
responseCodes: {}
limits: []
note: >-
  SUPERSEDES A SCAFFOLD. Until this pass this file declared X-RateLimit-Limit /
  X-RateLimit-Remaining / X-RateLimit-Reset / Retry-After / RateLimit-Policy
  headers and a 429 throttled response for a provider that returns no HTTP
  responses at all. Those values were written by the 2026-05-04 bulk sweep
  (method: generated) and were never observed. They are removed.
  DO NOT MISREAD THE CLI TIMEOUTS AS LIMITS. Dredd publishes several documented
  timing defaults — --hooks-worker-timeout 5000ms, --hooks-worker-connect-timeout
  1500ms, --hooks-worker-connect-retry 500ms,
  --hooks-worker-after-connect-wait 100ms, --hooks-worker-term-timeout 5000ms,
  --hooks-worker-term-retry 500ms, --server-wait 3s — but every one of them
  governs Dredd's own local IPC with a hooks handler process on 127.0.0.1:61321,
  not a quota any caller is subject to. They are captured in cli/dredd-cli.yml
  where they belong. Dredd also imposes no pacing on the requests it makes
  against the API under test; there is no --delay or --throttle option.