generated: '2026-09-18' method: probed source: >- Live unauthenticated responses from https://api.beamy.io/ and https://clientapi.prod.beamy.io/ (2026-09-18) plus a search of every public Beamy page and the public tier of docs.beamy.io. provider: Beamy providerId: beamy description: >- No Beamy rate limits are published, and no rate-limit signalling appears on any response an anonymous caller can obtain. The API edge is a Kong 3.9.3 gateway (server and x-kong-* headers) that refuses every request without a key, so whatever throttle it applies is invisible from outside. limit_count: 0 limits: [] response_headers: observed: [] checked: - X-RateLimit-Limit - X-RateLimit-Remaining - X-RateLimit-Reset - RateLimit-Limit - RateLimit-Remaining - RateLimit-Reset - RateLimit-Policy - Retry-After note: >- None present. Full anonymous response header set on https://api.beamy.io/ is: date, content-type, www-authenticate, content-length, x-kong-response-latency, server, x-kong-request-id, via, alt-svc. exhaustion_status_code: unknown exhaustion_envelope: >- Kong's key-auth plugin answers { "message": "...", "request_id": "..." } on the observed 401; a 429 from the same gateway would plausibly use the same envelope, but no 429 was induced and none is documented. evidence: - url: https://api.beamy.io/ status: 401 note: No rate-limit headers on the response; server kong/3.9.3. - url: https://clientapi.prod.beamy.io/ status: 401 note: No rate-limit headers; body {"statusCode":401,"message":"TOKEN_EMPTY"}. - url: https://docs.beamy.io/en/ status: 200 note: Public tier lists ten articles, none about the API; implementation docs need the lead form. - url: https://beamy.xyz/pricing status: 404 note: No pricing page, so no quota table either. note: >- limit_count 0 means "nothing published", not "no limits enforced". It replaces the 2026-05-04 scaffold whose per-tier limits (10/100/1000 rpm) were placeholders Beamy never published.