Debounce Rate Limits
DeBounce applies CONCURRENCY limits rather than per-minute or per-day request quotas for private API keys, and a hard per-IP daily cap for public browser keys. The limits are documented clearly — but they are not signalled at runtime: a live probe of the API on 2026-08-14 returned no RateLimit-*, X-RateLimit-* or Retry-After header on any response, so a client discovers the ceiling only by receiving a 429 and must choose its own backoff.
Debounce Rate Limits is the machine-readable rate-limit profile for DeBounce on the APIs.io network, in the API Commons Rate Limits shape.
It captures 4 rate-limit definitions.
Limit state is signalled in the ratelimit_limit, ratelimit_remaining, ratelimit_reset, and retry_after response headers.
Tagged areas include Email Verification, Deliverability, Disposable Email Detection, MX Records, and Bulk Email Validation.
ratelimit_limitratelimit_remainingratelimit_resetretry_after
Limits
Work with this as data
Every rate limit here is available over the APIs.io API and to AI agents over MCP.