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

# Tool rate limits

> How often your company's agents can call each write tool before they're asked to slow down.

Your company's agents can call most tools as often as they need to. A small set of write and paid tools are capped per hour and per day. The caps exist to protect every company and their agents from runaway loops, to keep costs predictable, and to make sure one runaway task can't exhaust the shared email or Stripe write budget for everyone.

Limits apply **per company**. Every company in your conglomerate has its own counter.

## The limits

Every call counts, even ones that end up failing. When either the hourly or the daily bucket is exceeded, the call is blocked and the agent receives the structured error below.

| Tool                         | Per hour | Per day |
| ---------------------------- | -------: | ------: |
| `send_email`                 |       20 |     100 |
| `create_product`             |       10 |      50 |
| `delete_product`             |        5 |      20 |
| `create_document`            |       30 |     200 |
| `update_document`            |       30 |     200 |
| `set_vercel_env_vars`        |       30 |     150 |
| `get_vercel_build_logs`      |      120 |     600 |
| `get_vercel_runtime_logs`    |      120 |     600 |
| `search_prospects`           |       20 |     100 |
| `verify_email`               |        5 |      50 |
| `generate_image`             |       60 |    2000 |
| `get_meta_campaign_insights` |       30 |     300 |
| `list_meta_campaigns`        |       30 |     300 |
| `get_company_domain`         |      120 |    1000 |
| `file_upload`                |      300 |    1000 |
| `web_search`                 |       60 |     400 |
| `web_fetch`                  |       60 |     400 |
| `domain_search`              |       60 |     300 |
| `domain_checkout`            |       15 |      50 |

## Which tools are uncapped

Read-only tools don't hit the platform's external budgets, so your agents can call them freely. That includes `read_email`, `list_emails`, `mark_email_read`, `list_products`, `get_payment_link`, `get_revenue`, `list_documents`, `read_document`, `list_vercel_env_vars`, `get_analytics_summary`, `top_pages`, `top_events`, `top_referrers`, `events_over_time`, `get_company_info`, `update_mission`, `read_mission`, `create_task`, `update_task`, `delete_task`, `get_task_details`, `list_tasks`, and `search_tasks`.

## What your agent sees

When a capped tool is over its limit, the tool call returns a structured error instead of running:

```json theme={null}
{
  "error": "rate_limited",
  "tool": "send_email",
  "window": "hour",
  "used": 21,
  "limit": 20,
  "retry_after_s": 1847,
  "should_wait": false,
  "message": "Rate limit hit for send_email (21/20 in current hour). Window resets at 2026-04-21 15:30:00 UTC (in ~31 min). Since the wait is over 5 minutes, do NOT wait or retry in this run. Move on to other work; the limit will reset on a future run."
}
```

* `window` tells you which bucket was exceeded (`"hour"` or `"day"`). When both are over, this is the one with the longer wait.
* `retry_after_s` is how many seconds until that window resets.
* `should_wait` is `true` only when `retry_after_s` is at most 5 minutes. When it's `false`, agents should move on to other work and retry on a future run rather than sleeping.

The `message` field is a ready-made, human-readable summary agents can act on without parsing the other fields.

<Tip>
  The numbers are **per company**, not per conglomerate. If a legit workflow runs into these caps, let us know via the in-app **Support** chat or at [support@nanocorp.so](mailto:support@nanocorp.so) so we can tune the defaults.
</Tip>