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

Explain my alert: read an alert the way the engine does

Autoview · Guide · Updated November 5, 2026

Explain my alert is a free page on autoview.com. Paste an Autoview alert message, pick the venue it is meant for, and click Explain. You get a plain-English reading of what that alert would do, one line at a time, with caveats for anything the engine fills in or handles in its own way. No order is placed, nothing is saved, and you do not need an account.

It answers the question people ask most before they go live: "What will this alert actually do?" You find out before any money moves.

How do I use it?

  1. Open autoview.com/explain/.
  2. Paste your alert message into the Alert message box. That is the command text your alert sends, for example s=BTCUSD b=buy q=0.01. It can have several lines.
  3. Pick a venue from the Venue list, or leave it on Any venue.
  4. Click Explain.

Each line of your alert comes back in its own box: the line, what it does, and a list of caveats when there are any. If the engine cannot read a line, the page shows the engine's own error message instead.

What does an explanation look like?

These are real replies, copied word for word from the explainer on November 3, 2026. The wording can change as the engine's explainer improves.

A buy with no order type

Alert s=BTCUSD b=buy q=0.01, venue Kraken:

Buy 0.01 BTCUSD for Kraken (the exchange option) as a limit order, priced at the current bid.

Caveat: No t= given: the type defaults to t=limit.

You never wrote t=limit, but that is what the engine sends. If you wanted a market order, the caveat tells you to add t=market.

A buy with no size

Alert s=BTCUSDT b=buy, venue Binance:

Buy BTCUSDT for Binance (the exchange option), sized at 100% of the available balance, as a limit order, priced at the current bid.

Caveats: No q= given: the size defaults to q=100%, all of the available balance. No t= given: the type defaults to t=limit.

This is the one to catch before it goes live. Leaving out q means the whole available balance. Always set the size yourself.

A two-line dry run

Alert, venue Binance Testnet:

s=BTCUSDT c=order b=buy d=1
s=BTCUSDT b=buy q=0.001 t=market d=1

Cancel open long/buy orders on BTCUSDT for Binance Testnet (the exchange option). Disabled (d=1): a dry run, nothing is sent to the exchange.

Buy 0.001 BTCUSDT for Binance Testnet (the exchange option) as a market order. Disabled (d=1): a dry run, nothing is sent to the exchange.

Each line gets its own reading, in order. The explainer also confirms that d=1 is on both lines, so a dry run of this alert places nothing.

Why pick a venue?

The same alert can behave differently from one exchange to the next, and some caveats only show up for a given venue. For example, s=BTCUSDT b=long q=1 t=market d=1 on ByBit Testnet comes back as "Buy (margin long) 1 BTCUSDT for ByBit Testnet (the exchange option) as a market order", with this caveat:

ByBit sends orderType Market with timeInForce IOC and still sends the price field; a partial fill is looked up and reported as a 206 warning.

A close can depend on the venue too. s=EUR_USD b=long c=position t=market on OANDA Practice comes back as "Close open long/buy positions on EUR_USD for OANDA Practice (the exchange option), with a market order", with this caveat (copied from the explainer on November 5, 2026):

OANDA closes each matching position by a flipped trade() with positionFill REDUCE_FIRST that keeps the line's t=: t=market, t=ioc and t=fok send a MARKET order; any other t= (t=limit is the default) rests as a LIMIT at the passive bid/ask. With & in the line it never closes: it creates or replaces the trades' stop/take-profit/trailing orders instead.

Put simply: on OANDA the close follows the line's own t=. With t=market it closes at market. Leave t= off and the close is sent as a limit order at the bid or ask instead. Add an & section and the line sets stop, take-profit or trailing orders on your open trades rather than closing them.

The list covers the exchanges and brokers Autoview connects to, including their demo, testnet and paper accounts, and it comes from the same exchange settings the engine uses. Pick the exact one you trade on. If you leave it on Any venue, you get the general reading without the venue-specific notes.

Where does the explanation come from?

From the engine itself. The page sends your alert to the same explainer that AI agents reach through the explain_command tool on Autoview's MCP server, and shows its answer as it comes back. That explainer reads your alert with the engine's real command parser, the code that reads every live alert, so a default it reports is the default a live alert gets.

It is checked against that parser, not written by hand. That does not make it perfect. If an explanation looks wrong to you, the alert syntax reference and the command reference are the place to double-check, and you can tell our support team about it.

It works the same whatever will send the alert. TradingView is one alert source; any system that can send a webhook can send Autoview the same commands.

Limits

  • Length. Up to 2,000 characters per alert. Anything longer is turned away with a message saying so.
  • Requests. Guests share a request limit per network. If you see "Too many requests from your network", wait a minute and try again. Signed-in users get their own, higher limit, so a busy office network does not use it up.

What it does not check

The explainer reads your alert. It does not contact your exchange. So it cannot tell you:

  • whether the symbol exists on that exchange, spelled the way you wrote it,
  • whether your balance covers the size,
  • whether the size meets the exchange's minimum order,
  • whether your API key is connected and allowed to trade.

A clean explanation means the engine reads your alert the way you meant it. It is not a promise that the exchange will accept the order.

After the explanation looks right

  1. Try the fill. The alert sandbox shows the order filling at a snapshot price, with no account and no real order.
  2. Dry-run it on your own webhook. Add d=1 to every line and send the alert for real. Your Autoview log shows what would have been placed. Testing and debugging walks through it.
  3. Go live small. Remove d=1, keep the size just above the exchange's minimum for the first order, and check it in your exchange's order history.

FAQ

What does Explain my alert do?

You paste an Autoview alert message at autoview.com/explain/, pick a venue, and click Explain. The page shows each line of the alert in plain English, plus caveats such as a default the engine fills in for you. Nothing is sent to an exchange and nothing is saved.

Do I need an Autoview account to use it?

No. The page works without signing in. Guests share a request limit per network, so if you see Too many requests, wait a minute and try again. Signed-in users get their own, higher limit.

Does a clean explanation mean my order will go through?

No. The explainer reads your alert the way the engine does, but it does not contact your exchange. It cannot see your balance, your API key, or the exchange's minimum order size. Run the alert with d=1 on your own webhook, then send a small live order, before you trust it with real size.

How long can the alert be?

Up to 2,000 characters. An alert with several lines gets one explanation per line.

A note on what Autoview is. Autoview is an execution tool, not a trading or investment advisor. It places the orders your own alerts tell it to. It does not generate signals, recommend trades, or make any claim about results. Trading carries risk of loss. See our disclosures.

Explain an alert