The automation spectrum
“Prediction market trading bot” can describe very different tools. At one end is an alert that tells a person a market moved. Next is an order rule that submits one instruction at a chosen price. Then comes conditional automation: a position is monitored and capital follows a pre-reviewed if/then path. At the far end is an autonomous agent that decides what to trade, how much to trade, and when to change its own plan.
Collapsing those categories into one label creates bad expectations. A bot that independently changes its thesis is not the same thing as a strategy builder that executes a thesis a user already specified. For event contracts, where resolution rules, liquidity, and timing can matter as much as a quoted probability, the distinction is especially important.
Miramarket is conditional automation, not a black box
Miramarket is designed for the middle of that spectrum. It is a visual prediction market strategy builder: users define the market, direction, allocation, triggers, and destinations for capital. The product then represents those choices as an action-and-condition tree that can be reviewed before deployment.
That is different from promising an autonomous Polymarket or Kalshi bot that finds trades on a user's behalf. Miramarket does not turn an unexplained model output into a position. It gives a human-readable structure to rules such as “if my position weakens below this price, return funds to the wallet” or “if it strengthens, protect part of the gain.”
A model protection rule with a real market reference
On July 17, 2026, Polymarket's Argentina-to-win-the-World-Cup YES market was quoted around 0.4115. A user who had independently chosen that market could decide that a move below 0.40 invalidates the original thesis enough to stop carrying the position. The rule below represents the mechanism, not an investment recommendation.
Model strategy
A visible conditional exit
If the observed YES price falls below 0.40, the illustrative $1,000 allocation routes to a USDC wallet. The trigger and destination are visible before deployment.
If the observed YES price falls below 0.40, the illustrative $1,000 allocation routes to a USDC wallet. The trigger and destination are visible before deployment.
A conventional limit order may be enough for a simple exit. The strategy-builder view becomes more useful when the condition leads to several deliberate actions, when a time rule needs to sit alongside a price rule, or when the same capital flow crosses supported venues. In every case, the system should preserve the reason a rule exists, not just the order it emits.
What automation cannot do for you
Automation does not make a market liquid, settle an ambiguous question, guarantee an order will fill, or establish that a strategy is legal in a user's jurisdiction. It cannot replace reading a market's resolution criteria or checking platform availability. A 0.40 trigger can be rationally chosen and still execute at an unfavorable price if conditions move rapidly or available liquidity changes.
The right role for conditional trading automation is disciplined execution of rules a user understands. Miramarket makes those rules inspectable, supports simulation before deployment, and keeps the user responsible for reviewing the strategy. That is a more useful promise than pretending every strategy needs an autonomous bot.