Misskey Rate Limits
Rate limit definitions for the Misskey API surface. Misskey is open-source software where each instance administrator configures rate limiting independently. The Misskey backend exposes rate limit information via standard response headers. Job queue rate limits (delivery, inbox, relationship) are configurable in the instance .config/default.yml. Per-endpoint endpoint-level rate limits are enforced by the backend and controlled via the roles system. Default values below reflect typical instance configurations; consult your specific instance's /api-doc for authoritative limits.
Misskey Rate Limits is the machine-readable rate-limit profile for Misskey on the APIs.io network, in the API Commons Rate Limits shape.
It captures 6 rate-limit definitions, across the default, job-queue, and role-based tiers, measuring requests_per_minute and jobs_per_second.
Limit state is signalled in the limit, remaining, reset, and retryAfter response headers, and an exhausted limit returns HTTP 429.
This profile was written by API Evangelist and has not been verified against a page the provider published; treat every limit as unconfirmed until a dated transcription replaces it.
The profile also includes 5 backoff/retry policies defined and response codes documented for throttled, quotaExceeded, and serviceUnavailable.
Tagged areas include Open-Source, Social Networks, Fediverse, Rate Limiting, and Quotas.
limitremainingresetretryAfter
generated, dated 2026-06-13.
Limits
Policies
Work with this as data
Every rate limit here is available over the APIs.io API and to AI agents over MCP.