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, in the API Commons Rate Limits shape.

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

Limit state is signalled in the limit, remaining, reset, and retryAfter response headers, and 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 3 backoff/retry policies defined and response codes documented for throttled and serviceUnavailable.

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

2 Limits Exhausted: HTTP 429 limitremainingresetretryAfter
Method: generated, dated 2026-05-22.
Written by API Evangelist on 2026-05-22 and not verified against a page the provider published. Treat every limit as unconfirmed until a dated transcription replaces it.
View Source
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

Work with this as data

Every rate limit here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for rate limits

4 MCP tools reach this
  • find_rate_limitsBrowse and filter every rate limit in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This rate limit 
curl "https://apis.io/api/v1/rate-limits/readme-rate-limits"
All rate limits 
curl "https://apis.io/api/v1/rate-limits?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.