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: ReadMe
providerId: readme
created: '2026-05-04'
# Provenance stamped 2026-08-11: this artifact was written by the API Evangelist
# bulk sweep dated 2026-05-04, not harvested from the provider. See roadmap#35.
method: generated
modified: '2026-05-22'
tags:
  - Documentation
  - Developer Hub
  - Rate Limiting
description: 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.
headers:
  limit: X-RateLimit-Limit
  remaining: X-RateLimit-Remaining
  reset: X-RateLimit-Reset
  retryAfter: Retry-After
responseCodes:
  throttled: 429
  serviceUnavailable: 503
limits:
  - tier: all
    name: ReadMe API Fair Use
    scope: api-key
    metric: requests_per_minute
    limit: documented-as-fair-use
    description: ReadMe enforces fair-use throttling on the v2 API. Honor 429 responses and the Retry-After
      header. Specific numeric thresholds are not published.
    applies:
      - ReadMe API
  - tier: all
    name: Metrics Ingestion
    scope: api-key
    metric: requests_per_second
    limit: high-volume
    description: The Metrics API at metrics.readme.io is designed for continuous high-volume log ingestion
      from server-side SDKs. Batching is recommended.
    applies:
      - ReadMe Developer Metrics API
policies:
  - name: Backoff Strategy
    description: Clients should implement exponential backoff with jitter and honor the Retry-After header.
  - name: Batching
    description: Metrics SDKs batch log entries to reduce request volume against /v1/request.
  - name: Fair Use
    description: ReadMe reserves the right to throttle abusive patterns; sustained high-volume traffic should
      be coordinated with ReadMe support.
sources:
  - https://docs.readme.com/main/reference/intro-to-the-readme-api
  - https://docs.readme.com/main/docs/sending-api-logs
maintainers:
  - FN: Kin Lane
    email: kin@apievangelist.com