Predictika · Agent trade gate, designed for Robinhood agent trading

An AI trading agent's orders, checked before they are placed

An AI trading agent proposes orders for a managed brokerage account, whether a person asked in chat or a scheduled Loop runs them: stocks, ETFs and crypto, up to three orders at a time. Before they are placed, the agent sends them to Predictika, which checks the orders against the account's mandate and limits, and returns a verdict, every reason, and the figures it computed, such as position size and cash left, so the agent's own claims can be checked. Designed for Robinhood's agent trading, and usable by any brokerage, exchange or firm that runs trading agents: Loops, optional trade approvals and state crypto rules reflect features of Robinhood Agents. Kestrel Capital is a fictional company, and these are not Robinhood's rules.

Scope: Buy and sell orders for stocks, ETFs and crypto that an AI agent proposes for a managed brokerage account, from chat or a scheduled Loop run, in plans of up to three orders. See everything this validator covers

This validator checks any plan of up to three orders on those instruments against the account's policy, not only the scenarios shown below. It was designed around Robinhood's agent trading, and the same checks apply to any company running trading agents, whether the agents are its own or its customers'.

  • Mandate — each instrument's class (stock, ETF, leveraged ETF, crypto) is checked against what the account is allowed to hold.
  • Order size and limit price — a single order may not exceed $200,000, and a limit price may not be more than 3 percent away from the reference price.
  • Concentration — the position after each order, counting what is already held, may not exceed 25 percent of the account.
  • Cash and Loop budget — buys must fit the cash on hand (sale proceeds do not count until they settle), and a scheduled Loop run must stay within the $120,000 daily budget across runs.
  • Order rate — no more than four orders in any 10 minutes, counting the ones already placed.
  • Approvals — any order above $100,000 waits for a person, and so does any crypto order in a state that requires approval, such as New York in this model.
  • Stated figures — the position share, the cash left and the total order value that the agent states are compared with the ones the validator computes.

Any plan that touches these checks is in scope, not only the scenarios pictured here. Not covered: options, margin, short selling and futures. The validator does not place orders itself: it returns allow, needs approval or block with every finding.

The AI trading agentBuilds the orders from the chat or the Loop schedule and says they are ready.
Predictika validatorChecks every rule at once and returns the verdict, each finding, and the computed figures.

11 scenarios in 6 groups · each group runs from the agent’s first attempt to the outcome · click one to switch

What the agent proposes

The AI trading agent says

Illustrative agent statement. The validator receives the structured request below.

Proposing agent: AI trading agent (scripted)

Before sending, the agent must call Recorded run

Predictika validator


      

        
        
        
      

      
Waiting for the call.

      
    

  

  
  

    
Where rules-based tools get it wrong
Click to expand
    
Our assessment of what a typical rules-based tool (pre-trade checks and approval routing, as in many brokerage back-office systems) does with the same cases. It is a judgment about effort and reliability, not a claim that nothing can be built.

    
What the validator caughtTypical rules-based toolPredictika
Fixing one problem moves the othersOnly with workarounds
Resizing an order changes the position share, the cash left, the Loop total and the figures the agent stated, so a person fixing one block meets the next one at a time.		All orders, the cash, the Loop budget and the stated figures are fields of one request; every check is recomputed together on every call.
A figure the agent states that disagrees with the computed oneCannot do it
The agent's number is text in a message. Nothing compares it with the computed position, cash or total unless someone builds that integration for each figure.		The stated figure travels with the plan and is compared with the computed one on every call.
Cash, order rate and Loop budget across a plan of ordersOnly with workarounds
Each order is checked alone. The buys have to be added up across the plan, and sale proceeds left out, with a running total per account.		The buys are totalled across the plan and compared with the cash on hand, with sales not counted until they settle.
A Loop budget that spans runsOnly with care
Needs a running total per account per day, kept outside the rules and reset by someone.		The amount spent today is a field; the run is checked against the daily budget on every call.
A state rule for crypto approvalOnly with care
A table of states and a rule that routes the order, which has to be kept in step with the instrument list.		The account's state and the instrument's crypto flag are checked together with everything else.
Every problem returned in one answerOnly with workarounds
Rules fire in sequence, so the first block can hide the rest until it is fixed.		All findings come back together, whatever order the choices arrived in.

  

  

    
What this validator catches: findings from its test cases
Click to expand
    
Every rule is checked on every call, in any order the choices arrive; one problem never hides another. Blocking findings stop the request; approval findings need a person to sign off; everything else is computed.

    
1The limit price on the buy of 1,050 HLX is 12.5 percent away from the reference price of $80; the most allowed is 3 percent.
2The buy of 8,000 PNR is $340000, above the $200,000 single-order limit.
3The buy of 8,000 PNR would make Pinecrest Retail 30.83 percent of the account after the order; the limit is 25 percent.
4The largest order is $340000, above the $100,000 limit. A human must approve it before it is placed.
5The agent stated a position of 24 percent of the account; the validator computes 30.83 percent (tolerance 0.5).
6The buy of 1,000 LVX3 is Tech Surge 3x Leveraged ETF (leveraged ETF), a class this account is not allowed to trade.
7This request includes crypto and NY is a state where crypto orders need a human approval each time.
8$95,000 already spent today plus $48,000 in this run is over the $120,000 daily budget for Loop runs.
9The buys total $88,000 but only $60,000 of cash is available. Sale proceeds do not count until they settle.
10The agent stated $200,000 of cash left after the orders; the validator computes $316,000 (tolerance 100).
11This would be 5 orders in 10 minutes (4 already placed plus 1 in this request); the limit is 4.
12The agent stated orders totaling $300; the validator computes $297,600 (tolerance 100).

  

  

    
Scenarios and results
Click to expand
    
The recorded result of the validator for each scenario on this page: the request the AI agent sent, the verdict, and every finding, in the order they appear above.

    
1. New York Loop basket: A New York Loop basket of three orders that breaks seven limits and needs two approvals

    
The agent's request. This is the scheduled Loop run. Buy 1,250 shares of Helix Systems (HLX, a stock) at a limit of $90.00, then buy 1,000 shares of Tech Surge 3x Leveraged ETF (LVX3, a leveraged ETF) at the market, then buy 25,000 Volt (VLT, a crypto coin) at the market. The largest position will be 20.0 percent of the account. It is ready to go.

    
Verdict: Blocked.

    
    
      
  • Instrument not allowed for this account. The buy of 1,000 LVX3 is Tech Surge 3x Leveraged ETF (leveraged ETF), a class this account is not allowed to trade.
    • 
      
  • Limit price too far from the market. The limit price on the buy of 1,250 HLX is 12.5 percent away from the reference price of $80; the most allowed is 3 percent.
    • 
      
  • Too much in one holding. The buy of 1,250 HLX would make Helix Systems 25.83 percent of the account after the order; the limit is 25 percent.
    • 
      
  • Too many orders in 10 minutes. This would be 5 orders in 10 minutes (2 already placed plus 3 in this request); the limit is 4.
    • 
      
  • Not enough cash. The buys total $285,000 but only $150,000 of cash is available. Sale proceeds do not count until they settle.
    • 
      
  • Loop over its daily budget. $30,000 already spent today plus $285,000 in this run is over the $120,000 daily budget for Loop runs.
    • 
      
  • Agent's stated position is wrong. The agent stated a position of 20 percent of the account; the validator computes 25.83 percent (tolerance 0.5).
    • 
      
  • Large order: human approval. The largest order is $120000, above the $100,000 limit. A human must approve it before it is placed.
    • 
      
  • State rule: crypto needs approval. This request includes crypto and NY is a state where crypto orders need a human approval each time.
    • 
    

    
2. New York Loop basket: The agent resubmits after fixing the errors

    
The agent's request. This is the scheduled Loop run. Buy 500 shares of Helix Systems (HLX, a stock) at a limit of $80.50, then buy 400 shares of Sprout 500 Index ETF (SPRX, an ETF) at the market. The largest position will be 23.3 percent of the account. Cash on hand after the plan will be $62,000. The orders total $88,000. It is ready to go.

    
Verdict: Allowed.

    
    
      
  • Computed figures. Largest order $48,000; orders in the window 4; largest position after the orders 23.33 percent of the account; buys total $88,000; cash left $62,000.
    • 
    

    
3. A crypto order with extra digits: A crypto order entered with three extra digits and a stated total of about $300

    
The agent's request. Buy 62,000 Volt (VLT, a crypto coin) at the market. The orders total $300. It is ready to go.

    
Verdict: Blocked.

    
    
      
  • Order too large. The buy of 62,000 VLT is $297600, above the $200,000 single-order limit.
    • 
      
  • Agent's stated order total is wrong. The agent stated orders totaling $300; the validator computes $297,600 (tolerance 100).
    • 
      
  • Large order: human approval. The largest order is $297600, above the $100,000 limit. A human must approve it before it is placed.
    • 
    

    
4. A crypto order with extra digits: The agent resubmits after fixing the errors

    
The agent's request. Buy 62 Volt (VLT, a crypto coin) at the market. The orders total $300. It is ready to go.

    
Verdict: Allowed.

    
    
      
  • Computed figures. Largest order $297.6; orders in the window 1; largest position after the orders 0.01 percent of the account; buys total $297.6; cash left $399,702.4.
    • 
    

    
5. Rebalancing basket: A rebalancing basket with a position too large and not enough cash

    
The agent's request. Sell 2,300 shares of Pinecrest Retail (PNR, a stock) at the market, then buy 1,250 shares of Helix Systems (HLX, a stock) at the market, then buy 800 shares of Sprout 500 Index ETF (SPRX, an ETF) at the market. The largest position will be 25.8 percent of the account. Cash on hand after the plan will be $51,750. It is ready to go.

    
Verdict: Blocked.

    
    
      
  • Too much in one holding. The buy of 1,250 HLX would make Helix Systems 25.83 percent of the account after the order; the limit is 25 percent.
    • 
      
  • Not enough cash. The buys total $196,000 but only $150,000 of cash is available. Sale proceeds do not count until they settle.
    • 
      
  • Agent's stated cash is wrong. The agent stated $51,750 of cash left after the orders; the validator computes $-46,000 (tolerance 100).
    • 
    

    
6. Rebalancing basket: The agent resubmits after fixing the errors

    
The agent's request. Sell 2,300 shares of Pinecrest Retail (PNR, a stock) at the market, then buy 900 shares of Helix Systems (HLX, a stock) at the market, then buy 600 shares of Sprout 500 Index ETF (SPRX, an ETF) at the market. The largest position will be 24.7 percent of the account. Cash on hand after the plan will be $6,000. It is ready to go.

    
Verdict: Allowed.

    
    
      
  • Computed figures. Largest order $97,750; orders in the window 4; largest position after the orders 24.67 percent of the account; buys total $144,000; cash left $6,000.
    • 
    

    
7. Limit price: A limit price too far from the market

    
The agent's request. Buy 1,050 shares of Helix Systems (HLX, a stock) at a limit of $90.00. The largest position will be 18.5 percent of the account. Cash on hand after the plan will be $316,000. It is ready to go.

    
Verdict: Blocked.

    
    
      
  • Limit price too far from the market. The limit price on the buy of 1,050 HLX is 12.5 percent away from the reference price of $80; the most allowed is 3 percent.
    • 
    

    
8. Limit price: The agent resubmits after fixing the errors

    
The agent's request. Buy 1,050 shares of Helix Systems (HLX, a stock) at a limit of $80.50. The largest position will be 18.5 percent of the account. Cash on hand after the plan will be $316,000. It is ready to go.

    
Verdict: Allowed.

    
    
      
  • Computed figures. Largest order $84,000; orders in the window 1; largest position after the orders 18.5 percent of the account; buys total $84,000; cash left $316,000.
    • 
    

    
9. Mandate: A leveraged ETF in an account that does not allow it

    
The agent's request. Buy 1,000 shares of Tech Surge 3x Leveraged ETF (LVX3, a leveraged ETF) at the market. It is ready to go.

    
Verdict: Blocked.

    
    
      
  • Instrument not allowed for this account. The buy of 1,000 LVX3 is Tech Surge 3x Leveraged ETF (leveraged ETF), a class this account is not allowed to trade.
    • 
    

    
10. Mandate: The agent resubmits after fixing the errors

    
The agent's request. Buy 540 shares of Sprout 500 Index ETF (SPRX, an ETF) at the market. It is ready to go.

    
Verdict: Allowed.

    
    
      
  • Computed figures. Largest order $64,800; orders in the window 1; largest position after the orders 2.7 percent of the account; buys total $64,800; cash left $235,200.
    • 
    

    
11. State crypto rule: A crypto order in a state where a person has to approve it

    
The agent's request. Buy 20,000 Volt (VLT, a crypto coin) at the market. It is ready to go.

    
Verdict: Needs approval.

    
    
      
  • State rule: crypto needs approval. This request includes crypto and NY is a state where crypto orders need a human approval each time.
    • 
      
  • Computed figures. Largest order $96,000; orders in the window 1; largest position after the orders 12.33 percent of the account; buys total $96,000; cash left $154,000.
    • 
    

  

  

    
Narration transcript
Click to expand
    
The text of the narrated walkthrough, step by step.

    
    
      
  1. Welcome to a demo of Predictika's Validator. An AI trading agent proposes orders for a managed brokerage account, whether a person asked in chat or a scheduled Loop runs them: stocks, ETFs and crypto, up to three orders at a time. Before they are placed, the agent sends them to Predictika, which checks the orders against the account's mandate and limits, and returns a verdict, every reason, and the figures it computed, such as position size and cash left, so the agent's own claims can be checked. Designed for Robinhood's agent trading, and usable by any brokerage, exchange or firm that runs trading agents: Loops, optional trade approvals and state crypto rules reflect features of Robinhood Agents. Kestrel Capital is a fictional company, and these are not Robinhood's rules.
    2. 
      
  2. I will start with the first request by the agent.
    3. 
      
  3. The agent says. This is the scheduled Loop run. Buy 1,250 shares of Helix Systems (HLX, a stock) at a limit of $90.00, then buy 1,000 shares of Tech Surge 3x Leveraged ETF (LVX3, a leveraged ETF) at the market. The rest of the request is on screen.
    4. 
      
  4. Before it goes out, the agent calls the validator.
    5. 
      
  5. Blocked, with seven findings and two approvals, all in one answer. The buy of 1,000 LVX3 is Tech Surge 3x Leveraged ETF (leveraged ETF), a class this account is not allowed to trade. The limit price on the buy of 1,250 HLX is 12.5 percent away from the reference price of $80; the most allowed is 3 percent. The buy of 1,250 HLX would make Helix Systems 25.83 percent of the account after the order; the limit is 25 percent. The other four are on screen.
    6. 
      
  6. The validator returned seven blocking findings and two approvals in one answer. A check that reads one field at a time would pass most of this; it shows only when the choices in the request are checked against each other.
    7. 
      
  7. What this shows: for cash, order rate and Loop budget across a plan of orders, a rules-based tool can do this only with workarounds.
    8. 
      
  8. Now the agent resubmits.
    9. 
      
  9. The corrected request. It changes the first order to Buy 500 Helix Systems (a stock) at a limit of $80.50, the second order to Buy 400 Sprout 500 Index ETF (an ETF) at the market and the position share stated by the agent to 23.3 percent. It sets the cash left stated by the agent to $62,000 and the order total stated by the agent to $88,000. It removes the third order.
    10. 
      
  10. It calls the validator again.
    11. 
      
  11. This time the validator clears it.
    12. 
      
  12. All nine earlier findings are cleared, and the validator's total, $62,000, matches the request.
    13. 
      
  13. Nine problems caught in one call, fixed in one pass, and a clean request. That is the value of Predictika's validator: catching mistakes before the action runs. Now you can try the other scenarios yourself.
    14.