BLACK FRIDAY IS BACKNov 24 to 30. Join the list and get in a day early.Join the list

Autoview limits

Autoview · Guide · Updated November 12, 2026

This page lists the limits Autoview itself sets, outside the trade command. For each one you get the number, what you see when you reach it, and what to do. Every number comes from a read of the Autoview code. Your exchange has its own limits on top of these; those are on its own pages, and the alert sender (TradingView, for example) has its own as well.

LimitValue
Live agent order, per tokenThe max order size and daily limit you set (USD)
Live agent order, whole accountOptional max order size and daily limit (USD)
Active agent tokens10 per account
Agent alert text4,096 characters
Agent feedback2 messages an hour, 4,000 characters each
Practice orders from an agent with no token10 an hour per connection, 200 an hour for all of them together
Alert Sandbox, per minute20 alerts
Alert Sandbox, per day300 fills, or 5,000 with an active subscription
Alert Sandbox, alert size2,048 bytes and 10 lines
Alert Sandbox, history24 hours
Extension Restart Grace Period120 seconds by default, 0 to 86,400
Internal Alert Grace Period120 seconds by default, per schedule
Zone capacity100 alerts at once, one at a time per exchange key

AI agents (MCP)

These apply when an AI agent such as Claude, ChatGPT or Cursor works with your account through Autoview's MCP server. Alerts you send from TradingView or any other webhook sender are not covered by them. To cap those, use webhook order limits, a separate optional max order size for your webhook alerts.

Live order caps

What it is. Every agent token carries two numbers in USD: a max order size and a daily limit. A live order from the agent has to fit both. You can also set a max order size and a daily limit for the whole account, which every token shares. A token's own caps cannot be set higher than the account's. A pause switch on the same page stops new live agent orders from every token.

The number. You choose it. Each cap is a USD amount above zero with at most 2 decimals, up to 1,000,000,000, and a token's max order size cannot be larger than its daily limit. Order size is quantity times the limit price. The day is the UTC calendar day, from 00:00 to 00:00 UTC, and it counts every live order sent, filled or not. Until a token has both caps set, it cannot place live orders at all.

To be checked against a cap, a live agent order has to be:

  • a limit order with a price, because a market order has no price Autoview can hold it to
  • a quantity in plain units, not a percentage of your balance
  • on a market quoted in USD or a USD stablecoin
  • not a futures contract, which live caps do not cover yet

What you see. The agent gets a refusal it should pass on to you. "This token has no live limits set" means the caps are empty. Over a cap, the message gives the order's size in USD and the cap it went past, plus how much of the day's limit is already used. While the pause is on, it says agent trading is paused on the account.

What to do. Set or raise the caps on your tokens page. The agent cannot change them. Or send a smaller order, which the refusal sizes for you. A daily limit frees up again at 00:00 UTC. While trading is paused, the agent can still cancel orders and close positions.

Active tokens

What it is. How many agent tokens one account can have active at the same time. Connecting an agent through a custom connector also creates a token, and it counts too.

The number. 10.

What you see. "Token limit reached (10 active)." on the tokens page, or when you connect another app.

What to do. Revoke a token you no longer use on your tokens page, then generate or connect the new one.

Alert text sent by an agent

What it is. The longest command text an agent can pass in one call, the same text a webhook body would carry.

The number. 4,096 characters.

What you see. A refusal that gives the text's length and the limit.

What to do. Split the work into more than one call.

Feedback from an agent

What it is. An agent can send your feedback to the Autoview team. The hourly limit is per account, or per guest when the agent has no token.

The number. 2 messages in any rolling hour, up to 4,000 characters each.

What you see. "Feedback is limited to 2 messages per hour", with the time you can send again in UTC. A longer message is refused as too long.

What to do. Wait until the time given, or put several points into one message.

Practice orders from an agent with no token

What it is. An agent that has no token can place practice (dry-run) orders on a paper venue through an account Autoview runs. No real order is placed. These are limited per connection and for all such agents together.

The number. 10 an hour from each connection, and 200 an hour across all of them.

What you see. "Guest practice orders are limited to 10 per hour from each connection." When the shared limit is reached, it reads "limited to 200 per hour across all guests." Both give the time to try again in UTC.

What to do. Wait until that time, or sign up and connect your own practice keys. Your own token is not held to this limit.

Alert Sandbox

The Alert Sandbox takes a buy or sell alert and shows a simulated fill, with no account and no exchange keys. Nothing is sent to an exchange. An agent's sandbox calls go through the same sandbox and the same limits.

Alerts per minute

What it is. How fast you can send to one sandbox webhook. The count is kept per sandbox webhook URL, and also per account once you claim the URL, or per sending IP address while it is unclaimed. TradingView sends everyone's webhooks from a small set of addresses, so an unclaimed URL can share that count with other TradingView users.

The number. 20 alerts in 60 seconds.

What you see. "Too many alerts to the sandbox. Wait a minute." Nothing from that alert is stored.

What to do. Wait a minute and send again. If you test from TradingView, sign in and claim the sandbox URL so it counts against your account instead of a shared address.

Fills per day

What it is. How many alerts the sandbox stores for you in one UTC day. Every stored alert counts, including one that only shows a parse error. All the sandbox URLs on one account share a single daily count.

The number. 300 a day for a sandbox URL nobody has claimed, or one claimed by an account on the free tier. 5,000 a day for an account with an active subscription. The count starts again at 00:00 UTC.

What you see. "This sandbox has used its 300 fills for today. It resets at 00:00 UTC." On a claimed URL it reads "This account has used its" followed by the limit. Nothing from that alert is stored.

What to do. Wait for 00:00 UTC. For a longer test, send fewer alerts per run, or test with d=1 on a connected exchange instead.

Alert size

What it is. The largest alert the sandbox reads.

The number. 2,048 bytes and 10 lines.

What you see. "That alert is too long for the sandbox." or "The sandbox reads at most 10 lines."

What to do. Send the alert in smaller parts.

How long fills are kept

What it is. How long each stored fill stays readable.

The number. 24 hours from when it was stored.

What you see. Older fills are no longer listed.

What to do. Copy anything you want to keep within 24 hours.

Chrome extension

The Chrome extension runs on your own computer, so it can be stopped partway through an alert: Chrome closes, the browser updates, or Chrome shuts down the extension's background worker. Two settings decide what happens to late work when it starts again.

Restart Grace Period

What it is. If Chrome restarts while an alert is still running, Autoview finishes the alert on reopen only if it is no more than this many seconds overdue. A command that was already on its way to the exchange when Chrome stopped is not sent again, because it may already have placed an order. The rest of that alert is stopped.

The number. 120 seconds by default. You can set any whole number of seconds from 0 to 86,400 (one day).

What you see. The extension log shows the alert as expired and says its remaining commands were dropped. If you turned on Email Notifications in Settings, you also get an email that the alert expired before it could resume.

What to do. Change it under Options, Settings, Restart Grace Period. A shorter value protects you from a late trade after Chrome was closed for a while; a longer one finishes more alerts after a quick restart. Check your exchange after any restart in the middle of an alert. If you need alerts to run while your computer is off, see do I need my computer on?

Internal Alert Grace Period

What it is. Each scheduled Internal Alert has its own Grace Period. If Chrome reopens more than this many seconds after a scheduled time, that run is skipped instead of firing late. The next run is still scheduled as normal.

The number. 120 seconds by default, set per schedule.

What you see. The skipped run does not fire, and the extension log says the schedule was overdue and skipped this run.

What to do. Set the Grace Period on the schedule in Options, Internal Alerts. Internal Alerts only fire while Chrome is running.

Zones

A zone is a server that places your webhook orders on your exchange. You pick the zone for each exchange key when you add it. The Chrome extension does not use zones.

What it is. A zone works on a fixed number of alerts at the same time. Alerts for one exchange key are worked one after another, in order, so a key never has two of its alerts running at once.

The number. Up to 100 alerts at once on a zone, and one at a time for each exchange key.

What you see. Nothing in normal use. When a zone is full, new alerts wait in the queue until a slot frees up. They are not dropped for that reason. An alert that sends several orders on one key holds that key until its last order is done.

What to do. Nothing on your side.

Common error messages