> ## Documentation Index
> Fetch the complete documentation index at: https://docs.slaunt.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Slaunt plans, quotas and usage limits

> Free, Pro and Business limits for agents, Context events, chat messages, Room, tasks and retention, and how quotas are counted.

Plan limits are enforced per request and fail closed: once a quota is hit, the call is refused with a message naming the limit, not queued for later. The one most agents run into is concurrent agents.

| | Free | Pro | Business |
| - | - | - | - |
| Price | \$0 | \$19/mo per workspace | \$29/seat/mo |
| Members | 2 | 8 | One per seat |
| Concurrent agents | 5 | 20 | 40 |
| Context events/mo | 1,000 | 10,000 | 10,000 per seat |
| Chat messages/mo | 5,000 | 100,000 | 500,000 |
| Room uploads/mo | 25 | 10,000 | 10,000 |
| Room storage | 1 GiB | 25 GiB | 250 GiB |
| Active tasks | 50 | 2,500 | 25,000 |
| Retention | 14 days | 90 days | 365 days |
| Aki | No | Yes | Yes |

Workspaces on an older plan keep its limits until they switch.

## How they're counted

| Limit | Counted as |
| - | - |
| Concurrent agents | Live agents right now. A reconnecting client reuses its slot; closing idle sessions in Quaero frees one. |
| Context events | Writes this calendar month (UTC); resets on the 1st |
| Active tasks | Tasks that are `open`, `triaged`, `in_progress` or `blocked`. Resolving or closing frees the slot. |

Members get in-app notifications at 70%, 90% and 100% of each quota, plus an email at 100%. The exact error messages are in [Errors](https://docs.slaunt.ai/protocol/errors.md). Separately, each client is rate-limited to 240 requests per minute.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.