Prelude So Rate Limits
Prelude does not publish fixed numeric per-endpoint rate limits in its public API reference. The API signals throttling with an HTTP 429 response (documented on the verification check endpoint). In practice, verification throughput is governed less by a request-per-second cap than by Prelude's own anti-fraud controls: create-verification can return statuses such as `blocked` or `shadow_blocked` and per-target retries are consolidated within a verification window rather than creating new verifications. Sustained volume and any account-level limits are handled through your plan and, on Enterprise, a 99.95% SLA.
Prelude So Rate Limits is the machine-readable rate-limit profile for Prelude on the APIs.io network, in the API Commons Rate Limits shape.
It captures 3 rate-limit definitions, measuring requests, verifications, and feedbacks.
An exhausted limit returns HTTP 429.
This profile was written by API Evangelist and has not been verified against a page the provider published; treat every limit as unconfirmed until a dated transcription replaces it.
The profile also includes 2 backoff/retry policies defined and response codes documented for throttled.
Tagged areas include Number Verification, OTP, Anti-Fraud, Rate Limiting, and Quotas.
generated, dated 2026-07-11.
Limits
Policies
Sources
- https://docs.prelude.so/verify/v2/api-reference/check-a-code
- https://docs.prelude.so/verify/v2/api-reference/create-or-retry-a-verification
- https://prelude.so/pricing
Work with this as data
Every rate limit here is available over the APIs.io API and to AI agents over MCP.