Paper Trade Kalshi and Polymarket: No-Code Testing and Limits (2026)
Paper trade supported Kalshi and Polymarket strategies in Turbine Studio. Compare simulated orders, Kalshi demo, fees, location restrictions, and live execution.

You can test a Kalshi bot without placing real orders by running a paper simulation or using Kalshi's separate demo environment with mock funds. Turbine Studio supports paper bots for evaluating supported strategies as new market data arrives. Paper results help you inspect behavior, but they do not prove that real orders will fill or that a strategy will make money.
This guide covers forward testing. For replaying historical data, use the backtesting guide. To compare bot software, see Kalshi bot features, costs, and testing.
Backtesting, paper trading, and Kalshi demo: what changes?
| Test | Data and execution | Useful for | Limitation |
|---|---|---|---|
| Historical backtest | Past market data with modeled fills | Checking rules across a stated historical window | Results depend on coverage, timing, and simulation assumptions |
| Paper bot | New market data with simulated orders and balance | Inspecting entries, skips, exits, and operational behavior | No real queue position, market impact, or execution guarantee |
| Kalshi demo | Separate exchange environment using mock funds | Testing authentication and order integration | Demo prices and behavior can differ from production |
| Live bot | Real orders against a funded account | Observing actual execution | Trading capital is at risk |
Kalshi's official demo documentation confirms that production and demo credentials are separate and warns that demo markets may behave differently. Its recommended REST root is https://external-api.demo.kalshi.co/trade-api/v2; the older demo-api.kalshi.co address is also supported. Developers should use the current API environments documentation when configuring their client.
Do not equate an exchange demo with a simulator using production prices. Also do not call a small real-money order a paper trade: it can execute and lose capital.
How to paper trade a Kalshi bot in Turbine Studio
1. Specify one strategy and inspect its rules
Choose Kalshi in Studio. Define the market, signal, entry price, exit, position limit, and conditions that skip an entry. Ask Studio to explain the draft before deploying. The build guide walks through this review.
2. Backtest where supported
Use historical testing to inspect data coverage and simulated trade behavior before starting a forward run. If the backtest is unavailable or inconclusive, retain that limitation in your evaluation rather than claiming that it passed. See backtest data sources and reading results.
3. Select paper mode and review deployment
Review the bot, mode, strategy rules, and limits in the deployment flow. Confirm paper mode before starting. A paper bot runs on your private Locus runner and counts toward your plan's concurrent bot allowance, across venues. See bot and runner limits and current pricing.
A strategy is the set of rules; a bot is a running instance. The same strategy can have separate instances, so check the target bot and mode rather than assuming a strategy title identifies the run you intend to inspect.
4. Read the decisions, including skipped actions
Check when the bot evaluated a market, which data it used, and why it entered, exited, or skipped. Compare logs with the rules you approved. Watch for stale signals, empty market selections, repeated failures, and unexpectedly inactive periods. The monitoring guide explains the available controls and logs.
5. Review the evidence before deciding on live operation
Record the paper window, markets, trade count, simulated costs, drawdown, and failures. A positive summary with no meaningful activity or incomplete logs is inconclusive. Live deployment is a separate user decision; Studio does not promise automatic paper-to-canary promotion based on a universal performance threshold.
Review running and stopping a bot before using live mode. Confirm the exact account, bot, credentials, and limits, and inspect open orders and positions when stopping. Stopping evaluation and closing existing exposure are different actions.
What to check in a paper-trading result
| Check | Question to answer |
|---|---|
| Rule fidelity | Do entries and exits match the approved draft? |
| Missing data | Does the bot skip or fail visibly when required data is stale or absent? |
| Fill assumptions | Is a simulated fill based on a tradable side of the book, and how is size treated? |
| Costs | Are the applicable fees and spread included? |
| Sample | Were there enough relevant decisions to inspect the intended behavior? |
| Recovery | Can you explain what happened after interruptions and restarts? |
| Stop behavior | What happens to new actions, open orders, and existing positions? |
Kalshi's official fee schedule is the source for exchange charges. Do not assume Kalshi trading is universally fee-free. A simulator's costs and fills need explicit review, even when its virtual PnL looks favorable.
There is no fixed Sharpe ratio, number of trades, or paper-to-live percentage that proves a bot is ready. The sample needs to cover the behavior you are trying to evaluate. A rare-event strategy may remain inconclusive even after many days with no trades.
Why a paper result can differ from live trading
A simulator does not hold a real place in the order queue. Available depth may change between observation and order arrival, partial fills can differ, and real orders can affect a thin book. Data outages, order rejection, settlement handling, and account constraints also matter.
Paper trading can reveal rule and operational problems before live orders. It cannot eliminate these execution differences. If your thesis depends on fills that the paper model cannot represent, treat that as an unresolved limitation.
For a concrete example of why one result is insufficient, compare our April Bitcoin study with the later public research review. Both report simulations, with different windows and assumptions; neither is a paper or live performance record.
Can I paper trade Polymarket without writing code?
Yes, Turbine Studio can generate a supported Polymarket strategy from a plain-English description and run it in paper mode. Choose the exact venue first: regular Polymarket and Polymarket US have different capabilities. A paper bot reads market data while simulating orders, fills, positions, and balance. It does not place real exchange orders.
- Open Studio and choose Polymarket or Polymarket US, according to the venue available to you.
- Describe the market, entry, exit, size, and skip conditions. Review the generated YAML strategy against the appropriate Polymarket examples or Polymarket US reference. The Polymarket backtesting guide compares Paper Runs with historical replay.
- Choose Paper Run in the deployment flow and confirm the target venue and bot. Check the strategy's own limits: regular Polymarket does not apply the deploy-dialog risk limits used by Kalshi and Polymarket US.
- Inspect simulated trades and decision logs. Report activity, failures, and skipped entries, alongside the simulation assumptions.
Location matters even for paper mode. Studio blocks regular Polymarket deployment from restricted locations, including the United States; this check includes paper bots. US users should review the separate Polymarket US workflow. The current venue documentation explains the restrictions; paper mode is not a way around them.
Fees matter when reviewing the result. Regular Polymarket paper bots pay no fees by default. Polymarket US paper fees are also zero, and its unrealized_pnl field reads zero in paper mode. Those assumptions differ from live trading. Review regular Polymarket fees and live differences and Polymarket US paper limitations before comparing virtual PnL with a live account.
Paper and live bots share your plan's concurrent allowance. See current pricing. Cross-venue arbitrage also has a Paper Run: each leg fills on its own against its venue's live order book and pays that venue's fees, so a lock can end with one leg filled and the other not, as it can live. It has no historical backtest.
Frequently Asked Questions
Can I paper trade a Kalshi bot before using real money?
Yes. Turbine Studio supports paper bots for supported strategies. Review paper mode and the target bot before deployment, then inspect simulated trades and decision logs. Kalshi also offers a separate demo environment with mock funds for testing exchange integration.
Is Kalshi demo the same as paper trading on live prices?
No. Kalshi demo is a separate environment with separate credentials. Kalshi warns that its market prices and behavior may differ from real markets. A paper simulator using new production data is another testing method, with its own fill assumptions.
Do Turbine paper bots count toward my plan limit?
Yes. Paper and live bots count toward the concurrent bot allowance across venues. Starter, Basic, and Pro have different caps; consult current pricing and the runner documentation before starting another bot.
Can I paper trade Polymarket without writing code?
Yes, for supported strategies and an available venue. Describe the rules in Turbine Studio, review the generated strategy, and choose Paper Run. Regular Polymarket paper deployment is subject to location restrictions, including a US block. Polymarket US is a separate venue with paper support. Paper fills and fees differ from live execution.
Can paper trading prove a bot will be profitable?
No. Paper fills and costs are modeled, and real execution can differ. Use paper trading to check behavior and identify problems, alongside supported historical tests. Positive simulated PnL is not a guarantee of live returns.
Does Studio automatically promote a paper bot to live trading?
No. Live deployment is a separate user decision. Review the target bot, credentials, execution mode, and limits before starting real orders; do not assume a paper result activates live trading.
