Open Payments Rate Limits
CMS Open Payments does not publish fixed numeric per-key rate limits, because the API requires no key or account. Practical throughput is governed by the page-size / limit parameters on each endpoint (search caps page-size at 100; datastore queries default to a 500-row limit and page via limit and offset) and by fair-use expectations for a shared public federal service. Very large pulls are better served by the CSV/JSON download endpoints or the bulk dataset files than by deep pagination of the query API.
Open Payments Rate Limits is the machine-readable rate-limit profile for CMS Open Payments on the APIs.io network, conforming to the API Commons Rate Limits specification.
It captures 3 rate-limit definitions, measuring rows, results, and requests.
The profile also includes 3 backoff/retry policies defined and response codes documented for throttled.
Tagged areas include Government Data, Healthcare, Open Data, Rate Limiting, and Quotas.
Limits
Policies
Sources
- https://openpaymentsdata.cms.gov/about/api
- https://dkan.readthedocs.io/en/latest/user-guide/guide_api.html
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.
Call it yourself
curl for this page
curl "https://apis.io/api/v1/rate-limits/open-payments-rate-limits"
curl "https://apis.io/api/v1/rate-limits?limit=25"
Discovery needs no key. Ratings and market analysis are Pro.