Rate limits & quotas
The exact free-beta quota numbers (200 queries/month, 100 pages indexed), the warning threshold, and what a 429 looks like.
Braize is free while in beta (see Pricing) with fair-use limits enforced by plan. These are the real numbers enforced today, not a vague "fair use" placeholder — they come from the same plan-limits table the gateway itself checks on every request.
Free-beta limits
| Limit | Cap |
|---|---|
| Queries per month | 200 (/v1/query, /v1/retrieve, and /v1/chat/completions all count against this) |
| Pages indexed | 100 (total across all connected sources) |
How enforcement works
- ≥ 80% of a limit — Braize starts recording an internal warning signal for your workspace once per limit per day. Nothing about your requests changes yet.
- ≥ 100% of a limit — the next request over the cap gets a
429RFC 9457 Problem instead of an answer:
{
"type": "https://braize.app/errors/quota-exceeded",
"title": "Plan quota exceeded",
"status": 429,
"detail": "The 'free' plan queries_month limit is reached (200/200). Upgrade your plan to continue."
}- There is no silent degradation — you either get a full answer or an explicit, typed error naming the limit you hit. See Handling errors for the general Problem shape.
- Limits reset monthly (queries) or are a running total (pages indexed, until you delete a document).
What's next
Paid tiers with higher caps are on the way — see Pricing for the
current state and the waitlist. api_mcp access itself is never gated
behind a paid plan; only the volume caps above change by tier.
Ingesting documents
Upload a file, ingest a URL, or manage documents via the API — parsing, sanitization, and chunking all run through the same pipeline.
Handling errors
Every Braize error is an RFC 9457 Problem Details object with a stable type URI — here is the shape and the type URIs that exist today.