---
title: Plans and limits
description: See how much each plan holds.
sidebar:
  order: 3
---

Limits apply to the whole organization and come from its plan. Prices are on [Pricing](https://www.siglata.com/en-US/pricing).

|                                 | Free    | Pro       | Enterprise           |
| :------------------------------ | :------ | :-------- | :------------------- |
| People                          | 1       | 1         | No limit             |
| Files, of any type              | 1 GiB   | 100 GiB   | 1 TiB, or as agreed  |
| Spreadsheets the agent queries  | 100 MiB | 1 GiB     | 10 GiB, or as agreed |
| Queryable cells per spreadsheet | 100,000 | 1,000,000 | 1,500,000            |
| Size of one queryable `.xlsx`   | 4 MiB   | 16 MiB    | 16 MiB               |
| MCP calls per week              | 100     | Unlimited | Unlimited            |
| Credits a month                 | 0       | 100       | 100, or as agreed    |

## At the limit [#at-the-limit]

- **Files**: any file type is accepted, up to 83,886,080,000 bytes each (78.125 GiB), and counts toward the plan's files, trash included. Without room, an upload fails with the `quota_exceeded` error and the link to change plans. Nothing is deleted: files stay available to read, query and download.
- **Spreadsheets the agent queries**: the cells read from spreadsheets and the tables the agent creates count here. Without room, uploads keep working: the file is stored with status `limit_reached`, its message carries the limit and the link to change plans, and Siglata reads it on its own, oldest first, as soon as there is room, whether after a plan change or deleting files or tables.
- **Large spreadsheets**: a spreadsheet over the cell or size limit is stored with status `too_large` and stays downloadable, but the agent does not query its cells. If the plan comes to allow it, it is read on its own. See the statuses in [Spreadsheets with SQL](/docs/en-US/agents/sql#readiness).
- **Calls**: each authorized `tools/call` counts as one call, however many operations its script runs, including when the script is invalid or permission is denied; `initialize`, `tools/list` and failures on our side do not count. The week starts over every Monday at 00:00, São Paulo time. Past 100 calls on Free, the call does not run and the agent gets a JSON-RPC error with `error.code` `-32000` and `error.data.code` `CALL_LIMIT_REACHED`, carrying the limit (`limit`), when the count starts over (`resetsAt` in ISO 8601 and `resetsAtLocal` spelled out) and the link to get Pro (`upgradeUrl`). After upgrading to Pro, the next call goes through; after returning to Free mid-week, the week's calls so far count.
- **Credits**: the organization has one credit balance for every paid operation. Today those are the `social_*` operations, which charge what each read of a social network, the news or reviews costs, in fractions of a credit. The plan's credits start over on the 1st of each month at 00:00, São Paulo time, and unused ones do not carry over. An owner of the organization buys packs of 1,000 credits on the Console's plan page, on any plan; bought credits never expire and are used only after the month's. With no credits left, the operation refuses with `CREDITS_EXHAUSTED` before reading any network; the page to buy more is `principal_get`'s `billingUrl`.
- **When Pro ends**: when the subscription ends, the organization returns to Free limits without losing files.

Pro is subscribed in the [Siglata Console](https://www.siglata.com/app). For the Enterprise plan, talk to us on WhatsApp from [Enterprise](https://www.siglata.com/en-US/empresas).