How the knowledge budget works, what a chunk is, and what happens when you hit the cap.
Each plan includes a knowledge budget per agent, measured in chunks.
What a chunk is
When we train on a website, file, or text source, we break it into small pieces of roughly 1,500 characters each. Each piece is a chunk. A short page might be one chunk; a long document might be dozens. The chunk count on each source in your Knowledge list tells you how much of your budget it uses.
Quick answers and quick links do not count against the chunk budget. They are direct sources, stored separately.
The limit per plan
| Plan | Chunks per agent |
|---|---|
| Free | 500 |
| Starter | 2,500 |
| Growth | 25,000 |
| Scale | 50,000 |
| Enterprise | Unlimited |
The stat strip at the top of the Knowledge page shows your current usage against the limit.
Hitting the cap
If an ingest would push you over the limit, it is stopped before anything is written, and you see an upgrade prompt. A few things soften this:
- Re-saving a source is not blocked. Replacing a file or text source swaps its chunks in place, so a re-ingest does not fail just because you were already near the cap.
- Scanning is always free. A website scan never counts against your budget. Only the pages you confirm to index do, so you can scan widely and index selectively.
If you are regularly near the cap, that is usually the signal to move up a plan. See Plans.