Recharge Payments Rate Limits
The Recharge API is throttled with a leaky-bucket algorithm. Each store token has a bucket that holds up to 40 requests and leaks (empties) at 2 requests per second. A steady rate of 2 requests/second will never trip a limit; short bursts up to the bucket size of 40 are allowed and then refill at 2/second. When the bucket overflows, the API responds with HTTP 429; the guidance is to sleep at least 2 seconds and retry. Higher Recharge plan tiers (Plus, Custom) may be granted higher API rate limits.
Recharge Payments Rate Limits is the machine-readable rate-limit profile for Recharge on the APIs.io network, conforming to the API Commons Rate Limits specification.
It captures 4 rate-limit definitions, measuring requests.
The profile also includes 3 backoff/retry policies defined and response codes documented for throttled.
Tagged areas include Subscriptions, Recurring Billing, E-commerce, Rate Limiting, and Quotas.
Limits
Policies
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.
Call it yourself
curl for this page
curl "https://apis.io/api/v1/rate-limits/recharge-payments-rate-limits"
curl "https://apis.io/api/v1/rate-limits?limit=25"
Discovery needs no key. Ratings and market analysis are Pro.