Lemmy Rate Limits
Lemmy rate limits are configured per instance by the instance administrator and enforced at the application layer. Default values observed from public instances (including lemmy.world running v0.19.18) cover message sending, posting, registration, image uploads, comments, and search. There is no global Lemmy rate limit; each instance operator may tune or disable limits. Exceeded limits return HTTP 429 Too Many Requests.
Lemmy Rate Limits is the machine-readable rate-limit profile for Lemmy on the APIs.io network, conforming to the API Commons Rate Limits specification.
It captures 6 rate-limit definitions, measuring requests.
The profile also includes 4 backoff/retry policies defined and response codes documented for throttled.
Tagged areas include Communities, Federated, Fediverse, Rate Limiting, and Social Networks.
Limits
Policies
Sources
- https://lemmy.world/api/v3/site
- https://github.com/LemmyNet/lemmy/issues/290
- https://github.com/LemmyNet/lemmy
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/lemmy-rate-limits"
curl "https://apis.io/api/v1/rate-limits?limit=25"
Discovery needs no key. Ratings and market analysis are Pro.