specification: API Commons Rate Limits specificationVersion: '0.1' schema: https://raw.githubusercontent.com/api-evangelist/interface-research/main/schema/api-commons.yml#/$defs/RateLimits provider: Elk providerId: elk created: '2026-05-04' modified: '2026-08-27' generated: '2026-08-27' method: probed source: >- Live unauthenticated GET https://elk.zone/api/list-servers (HTTP 200, 2026-08-27, full response headers captured) plus a documentation search across https://docs.elk.zone and https://github.com/elk-zone/elk for published limits. limit_count: 0 note: >- CORRECTION, 2026-08-27. This file previously carried five fabricated limits — 10 req/min and 1,000 req/month "free", 100 req/min and 100,000 req/month "professional", 1,000 req/min "enterprise", all keyed to an api-key scope Elk does not issue — written by the 2026-05-04 bulk scaffold sweep. None of them exist. They were replaced with this measured zero. Elk publishes no rate limits and returns no rate-limit headers. THIS IS AN HONEST ZERO, NOT AN UNCHECKED ONE: a live 200 was captured and its headers read. The limits that actually govern an Elk session are enforced by the user's own Mastodon instance against their own token, not by Elk. limits: [] headers: limit: null remaining: null reset: null retryAfter: null policy: null observed_headers: url: https://elk.zone/api/list-servers status: 200 observed: '2026-08-27' rate_limit_headers_present: false headers_seen: - cache-control - cache-status - etag - last-modified - netlify-vary - nel - referrer-policy - x-content-type-options - x-download-options - x-frame-options - x-permitted-cross-domain-policies - x-xss-protection - cf-cache-status - cf-ray - alt-svc - access-control-allow-origin responseCodes: throttled: null quotaExceeded: null policies: [] upstream_limits: - name: Mastodon instance rate limits enforced_by: the user's chosen Mastodon-compatible server, not Elk reference: https://docs.joinmastodon.org/api/rate-limits/ note: >- Every Elk feature beyond the sign-in picker is a call to the user's instance, carrying that instance's own limits and its own X-RateLimit-* headers. They vary per instance and are outside Elk's control. edge: provider: Netlify (origin) behind Cloudflare note: >- Infrastructure-level abuse protection may exist at the edge, but no limit, window, or header is published or observable, so none is recorded. maintainers: - FN: Kin Lane email: kin@apievangelist.com