ReadMe · Rate Limits

Readme Rate Limits

Machine-readable rate-limit definitions for ReadMe's developer-facing APIs. ReadMe does not publish granular numeric rate limits on its public pricing or docs; ReadMe API limits are enforced as fair-use throttling signaled via standard rate-limit response headers and 429 status codes. The Metrics ingestion endpoint is designed for high-volume per-request logging from server-side SDKs.

Readme Rate Limits is the machine-readable rate-limit profile for ReadMe on the APIs.io network, conforming to the API Commons Rate Limits specification.

It captures 2 rate-limit definitions, across the all tier, measuring requests_per_minute and requests_per_second.

The profile also includes 3 backoff/retry policies defined and response codes documented for throttled and serviceUnavailable.

Tagged areas include Documentation, Developer Hub, and Rate Limiting.

2 Limits Throttle: 429
DocumentationDeveloper HubRate Limiting

Limits

ReadMe API Fair Use api-key
requests_per_minute
documented-as-fair-use
Metrics Ingestion api-key
requests_per_second
high-volume

Policies

Backoff Strategy
Clients should implement exponential backoff with jitter and honor the Retry-After header.
Batching
Metrics SDKs batch log entries to reduce request volume against /v1/request.
Fair Use
ReadMe reserves the right to throttle abusive patterns; sustained high-volume traffic should be coordinated with ReadMe support.

Sources