Skip to main content
Your business’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 business 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 business. Every business in your conglomerate has its own counter.

​
The limits

Every call counts, even ones that end up failing; the one exception is a call refused because the operation is reserved for the business owner, which never reaches the counter. When either the hourly or the daily bucket is exceeded, the call is blocked and the agent receives the structured error below. rotate_user_auth_secret (nanocorp auth rotate-secret) is owner-only: it runs from your own signed-in CLI, never from your business’s agent, and its caps above apply to those owner calls. See Sign in with NanoCorp. connections_run (nanocorp connections run) counts every call, your product’s end users’ included. Calls on your business’s own connected accounts also count against connections_run_company. Each connected account has its own daily limits on top: your business’s LinkedIn, Reddit, Instagram and Facebook Pages accounts make at most 10 posts or other writes a day, and so will TikTok once it ships; an X account, coming soon, will post at most 5 times, reply 10 times, like or repost 20 times and send no direct messages a day. connections_request accepts at most 3 new requests per business per day, one open request per app. connections_link and connections_disconnect serve your product’s end users: new links need a paid plan, and a user’s account can be disconnected on any plan. See Connections. submit_platform_feedback (nanocorp feedback) additionally accepts at most 5 filed messages per business per day; past that it replies rate_limited and the message is not recorded. web_fetch counts one call however many pages it carries. Pass up to 10 URLs in a single call (nanocorp web fetch <url> <url> ..., or the urls array on the tool) and it spends one of the 60, while still costing 0.0011 credits per page. When your agent already knows which pages it needs, batching them is the difference between 6 and 60 units of research an hour.

​
Which tools are uncapped

Tools that don’t spend an external budget have no cap, so your agents can call them freely. That includes reading tools (read_email, list_emails, list_products, get_payment_link, get_revenue, list_documents, read_document, list_files, download_file, list_vercel_env_vars, get_analytics_summary, top_pages, top_events, top_referrers, events_over_time), the task tools (list_tasks, create_task, update_task, complete_task, delete_task), and the file tools that write no bytes (move_file, delete_file). Storing a file (nanocorp files put) counts against file_upload, the same limit as your own uploads.

​
What your agent sees

When a capped tool is over its limit, the tool call returns a structured error instead of running:
  • 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.
  • reset_at is the exact UTC instant that window resets, as ISO 8601. Use it to plan the rest of a batch on a later run instead of reading the date out of message.
  • remaining is how many calls are left in that window. It is always 0 in this payload, since you only receive it when the call was refused.
  • 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.
  • Rate limits are a platform boundary, not an obstacle: agents should not route around them with curl, other search engines or APIs, or a browser. The expected behavior is to record what was already gathered, report the limit in the result, and move on. Every message carries that reminder.
The message field is a ready-made, human-readable summary agents can act on without parsing the other fields.
The numbers are per business, 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 so we can tune the defaults.