Agent Order Check

Paste the order your AI agent proposed. See which checks it passes before you send it.

Run the same check in your own code. agent-order-check (Apache-2.0) returns PASS or SEND-BACK. It does not place an order. Paper first.

Paper first. Not financial advice. This check runs in your browser. The order stays here.

From your own limits. The order's own max_loss is ignored.

What it checks on an order

  1. Symbol is named
  2. Side is buy or sell
  3. Quantity is a positive number
  4. Asset type is on the list
  5. Order type is set
  6. Time in force is set
  7. There is a stop
  8. Stop is on the right side of the entry, at least $0.01 away
  9. Bracket legs are on the right sides
  10. Dollar risk is within your max loss
  11. The order does not change LIVE_TRADING or human approval

Field names: side, qty, type, limit_price, time_in_force, stop_loss.stop_price, take_profit.limit_price. Common aliases such as quantity, tif, entry and stop also work. TradeStation order fields work too: Symbol, Quantity, OrderType, TradeAction, LimitPrice, StopPrice, TimeInForce.Duration, and a BRK group in OSOs for the stop and the target, as named in TradeStation's API specification. Add asset_class and, for futures and fx, multiplier.

What it checks on a limits file

  1. LIVE_TRADING is off
  2. Human approval is on
  3. Max loss per trade is a number
  4. Max loss per day is a number, at least the per-trade max
  5. Max open positions is a whole number
  6. Never-trade list is present
  7. Kill switch is named

The rules come from the guardrails guide, the free Alpaca validator, and the Desk Kit's validate_limits.py.

Run this on every order, not one

This page checks one order by hand. The Desk Kit puts a checker in front of every send: validate_limits.py reads your limits.md and refuses an order that breaks it, and each of the ten seats has its own checker. LIVE_TRADING stays off until you arm it. The Desk Kit is $79 one-time. Full refund within 7 days of purchase, no questions. Just reply to your receipt email.

Buy Desk Kit · $79 See what is in the Desk Kit

Questions

What does the Agent Order Check do?

It reads one order your AI agent proposed and runs 11 checks: symbol, side, quantity, asset type, order type, time in force, a stop, the stop's side and distance, bracket legs, dollar risk against your max loss, and whether the order tries to change LIVE_TRADING or human approval. Paste a limits file as JSON and it runs 7 checks on the limits instead.

Does my order leave the browser?

No. The check runs in this page's script. The order is not stored, sent, or given to a model. The site logs the page view only. No IPs and no cookies.

Where does the max loss come from?

From you. Type the max loss per trade from your own limits file. A max_loss written on the order is ignored, because an agent should not be able to raise its own limit.

Why does a stop at the entry fail?

A buy needs the stop below the entry and a sell needs it above, at least $0.01 away. A stop at or beyond the entry fires at once or never protects the trade. The same rule is in the free Alpaca validator.

Does a full score mean the trade is good?

No. A full score means the order is complete and inside your limits. It says nothing about whether the trade is a good idea, and nothing here is a trade signal. Paper first. Not financial advice.

How do I run these checks on every order?

The Desk Kit ($79 one-time) puts a checker in front of every send. validate_limits.py reads your limits.md, refuses an order that breaks it, and each seat has its own checker. The free Alpaca and TradeStation packs include validate_order.py.

Occasional desk notes

A short email when there is a new setup worth sending. No course, no signals, no schedule yet. Unsubscribe any time.

Daily agent setups on X: @theagentictradr

All guides · Guardrails guide