Zinrelo Rate Limits
Zinrelo does not publish specific numeric per-account or per-endpoint rate limits in its public API reference. The documentation groups endpoints into rate-limiting categories (for example a General API category referenced on the rewards endpoint), which implies category-based throttling, but exact request ceilings and windows are not published. Callers should implement pagination (start_cursor and count) on list endpoints, cache reward and tier data that changes infrequently, and apply exponential backoff on throttle responses.
Zinrelo Rate Limits is the machine-readable rate-limit profile for Zinrelo on the APIs.io network, conforming to the API Commons Rate Limits specification.
It captures 2 rate-limit definitions, measuring requests and records.
The profile also includes 3 backoff/retry policies defined and response codes documented for throttled.
Tagged areas include Loyalty, Rewards, Rate Limiting, and Quotas.
Limits
Policies
Sources
- https://zinrelo.github.io/slate/
- https://help.zinrelo.com/reference/introduction
- https://help.zinrelo.com/reference/list-all-rewards
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/zinrelo-rate-limits"curl "https://apis.io/api/v1/rate-limits?limit=25"Discovery needs no key. Ratings and market analysis are Pro.