Brewpage Rate Limits
BrewPage relies primarily on hard structural caps (TTL, per-namespace counts, per-file size) and on User-Agent validation rather than on published numeric rate limits. The service reserves the right to throttle or reject anonymous or spoofed User-Agent requests and to flag abusive usage based on its 30-day access log.
Brewpage Rate Limits is the machine-readable rate-limit profile for BrewPage on the APIs.io network, in the API Commons Rate Limits shape.
It captures 11 rate-limit definitions, measuring request, result-set, day, byte, and file.
Limit state is signalled in the requestId response header, 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, unauthorized, badRequest, notFound, payloadTooLarge, unsupportedMediaType, and conflict.
Tagged areas include Rate Limiting, Hosting, and Anti-Abuse.
requestId
generated, dated 2026-05-16.
Limits
Policies
Sources
- https://brewpage.app/llms.txt
- https://brewpage.app/llms-full.txt
- https://brewpage.app/api/openapi.yaml
Work with this as data
Every rate limit here is available over the APIs.io API and to AI agents over MCP.