12. Limits and fair use#

Per-workspace bands (visible in errors): document count, questions per month, crawl size per source, request burst. Every path that spends model budget is throttled against them — the dashboard's Ask, the API routes, and every MCP tool that touches an embedding or chat model (search, remember, author, context) all draw on the same per-workspace bands, so no surface is a side door around the limits. Over-limit calls fail cleanly with an actionable message (HTTP 429 / MCP tool error).

Bands are tunable per workspace by admins — there are no universal numbers to quote here (defaults are set at provisioning and can be adjusted for your workspace). One crawl runs at a time per workspace — a second gets "a crawl is already running…" and can be retried after. These keep one workspace from degrading others.