Cross-Platform Prediction Arbitrage: Limit Order Quick Reference

# Cross-Platform Prediction Arbitrage: Limit Order Quick Reference **Cross-platform prediction arbitrage** is the practice of simultaneously buying and selling contracts on the same underlying event across two or more prediction market platforms to lock in a risk-free profit from price discrepancies. When Platform A prices an event at 42¢ and Platform B prices the same event at 51¢, a trader who buys on A and sells on B captures a 9-cent spread — minus fees. Limit orders are the precision tool that makes this repeatable, scalable, and low-stress without requiring you to stare at screens all day. --- ## Why Limit Orders Are the Backbone of Prediction Arbitrage Market orders feel intuitive — you click, you fill. But in prediction markets, market orders are a fast way to get slippage-burned and obliterate your edge. **Limit orders** let you define the exact price you're willing to pay or accept, which is critical when your entire profit margin might be just 4–8 cents per share. When you're running a cross-platform arb, your workflow essentially becomes: - Post a **resting limit order** on the higher-priced platform to sell (or "No" position) - Post a matching limit order on the lower-priced platform to buy (or "Yes" position) - Wait for both legs to fill near-simultaneously - Collect the spread The catch is coordination. If one leg fills and the other doesn't, you're left with **one-sided exposure** — which is no longer arbitrage, it's just a directional trade. This is why understanding fill probability, order depth, and cancellation mechanics is non-negotiable before scaling up. --- ## Key Platforms and Their Limit Order Mechanics Not all prediction market platforms handle limit orders the same way. Below is a quick-reference comparison of the major venues: | Platform | Limit Orders | Fee Structure | API Access | Best For | |---|---|---|---|---| | **Polymarket** | Yes (CLOB) | ~2% maker/taker | Yes (full REST) | High-volume event markets | | **Kalshi** | Yes | 1–7% per trade | Yes (REST + WebSocket) | Regulated US markets | | **Manifold** | Yes (play money) | None | Yes | Strategy testing | | **PredictIt** | Yes | 10% profit fee + 5% withdrawal | Limited | US political events | | **Metaculus** | No (point-based) | None | Yes (read-only) | Calibration research | **Polymarket** uses a **Central Limit Order Book (CLOB)** model, meaning your limit orders sit in a public order book and fill against counterparty orders. Kalshi uses a similar model with regulated US market structure. These two platforms represent the most liquid cross-platform arb opportunities right now. For a deeper breakdown of how these two venues compare head-to-head, check out this guide on [smart hedging between Polymarket and Kalshi for institutions](/blog/smart-hedging-polymarket-vs-kalshi-for-institutions). --- ## Identifying a Valid Arbitrage Opportunity Not every price gap is an arb. Here's how to evaluate whether a discrepancy is real, exploitable, and worth the execution risk. ### Step 1: Check the Same Resolution Criteria Markets resolving on different question definitions are **not** the same market. A Kalshi contract on "Will the Fed raise rates in September?" may resolve differently than a Polymarket version if the resolution sources differ. Read both fine-print sections before assuming equivalence. ### Step 2: Calculate the Net Edge After Fees Use this formula: **Net Edge = (Sell Price on High Platform) − (Buy Price on Low Platform) − (Total Fees)** If Polymarket shows YES at 44¢ and Kalshi shows YES at 55¢: - Buy YES on Polymarket at 44¢ - Sell YES on Kalshi at 55¢ - Gross spread: 11¢ - Estimated fees (both sides, ~3% combined): ~3¢ - **Net edge: ~8¢ per share** An 8-cent edge on a $1 binary is an **8% return** — excellent. Anything below 3¢ net is usually not worth the execution risk. ### Step 3: Check Liquidity Depth A 55¢ offer on Kalshi means nothing if only 50 shares are available. Use each platform's order book view or API to confirm you can fill your desired size at or near the posted price. ### Step 4: Estimate Time to Fill Cross-platform arbs depend on **simultaneous fills**. If one market is highly liquid and the other is thin, one leg may take hours or days to fill — during which the price may move against you. --- ## Setting Up Your Limit Orders: A Step-by-Step Process Here's the workflow to execute a cross-platform prediction arbitrage trade with limit orders: 1. **Identify the price gap** — Use a monitoring tool or manually compare the same event on two platforms. A gap of at least 5¢ net of fees is your minimum threshold. 2. **Confirm identical resolution criteria** — Read both market descriptions. If they differ, stop. 3. **Assess order book depth** — Confirm enough liquidity exists on both sides to fill your target position size. 4. **Calculate max position size** — Don't exceed available liquidity. A common rule: take no more than 20–30% of visible depth to avoid moving the market. 5. **Post the sell limit order first** — On the higher-priced platform, post your limit sell at your target price. This leg is usually harder to fill (you're selling at a premium). 6. **Post the buy limit order immediately after** — On the lower-priced platform, post your limit buy at your target price. 7. **Monitor fill status** — Check both legs within 5–10 minutes. If the sell leg fills but the buy leg hasn't, lower your buy limit slightly. 8. **If one leg fills and the other stalls for over 30 minutes** — Consider canceling the unfilled leg or accepting partial exposure if the directional view is acceptable. 9. **Record the trade** — Log both fills, timestamps, platform, fees paid, and net P&L. This data is invaluable for refining your strategy. 10. **Repeat and scale** — Once you have 10–20 successful trades logged, begin increasing position sizes in 25% increments per successful batch. For a more detailed guide on scaling this process up systematically, read [Scale Up with Cross-Platform Prediction Arbitrage & Limit Orders](/blog/scale-up-with-cross-platform-prediction-arbitrage-limit-orders). --- ## Common Mistakes That Kill Arb Profits Even experienced traders make these errors. Knowing them in advance saves real money. ### Ignoring the Withdrawal Timeline Some platforms (especially PredictIt) have withdrawal delays of 3–5 business days. If your capital is locked on one platform post-trade, your ability to deploy the same funds for the next arb is reduced. **Capital velocity** matters as much as edge per trade. ### Treating Every Price Gap as Exploitable Prediction markets sometimes show stale prices because a market is illiquid or barely monitored. A 15¢ gap that's been sitting for two days isn't necessarily free money — it may reflect genuine uncertainty, different interpretations of resolution criteria, or simply a ghost market. Always verify. ### Underestimating Execution Slippage Posting a limit order is not the same as guaranteeing a fill at that price. In fast-moving markets (election nights, major news events), prices can reprice before your orders are processed. This is especially true on platforms with slower API response times. ### Forgetting Tax Implications Prediction market profits are taxable in most jurisdictions, and cross-platform arb adds complexity because you're generating many small realized gains. Keeping clean records is essential. For a thorough breakdown, see this article on [prediction market profits and taxes for API traders](/blog/prediction-market-profits-taxes-what-api-traders-must-know). --- ## Automating Cross-Platform Arb with Bots and APIs Manual arb is viable at small scale, but to compete with professional traders you'll eventually need automation. Here's what a basic arb bot does: - **Polls both platforms' APIs** every 5–30 seconds for price updates on tracked markets - **Calculates net edge** in real time, accounting for fees and estimated slippage - **Posts limit orders** via API when edge exceeds a predefined threshold - **Monitors fill status** and cancels or adjusts unfilled legs - **Logs all activity** to a database for performance analysis [PredictEngine](/) is built specifically for this kind of automated prediction market trading, with tools for limit order management, multi-platform monitoring, and strategy backtesting. Its architecture makes it straightforward to implement the kind of arb logic described in this guide without building everything from scratch. If you're newer to prediction market trading automation, start with the [swing trading predictions quick reference guide for new traders](/blog/swing-trading-predictions-quick-reference-guide-for-new-traders) before diving into full automation — it covers the conceptual foundations that make bots perform correctly. You should also consider reviewing the [trader playbook and natural language strategy compilation](/blog/trader-playbook-natural-language-strategy-compilation) for additional strategy templates you can plug directly into automation workflows. --- ## Sizing, Risk Management, and Portfolio Allocation Even "risk-free" arb carries operational risk. Here's a sensible allocation framework: | Risk Category | Example | Mitigation | |---|---|---| | **Leg mismatch risk** | Buy fills, sell doesn't | Cancel unfilled leg; accept directional exposure | | **Platform risk** | Exchange halts withdrawals | Never allocate >30% to one platform | | **Liquidity risk** | Can't fill desired size | Size to visible order book depth | | **Resolution risk** | Markets resolve differently | Verify criteria before entering | | **Counterparty risk** | Platform insolvency | Prefer regulated venues (Kalshi) for large positions | A conservative rule for beginners: allocate no more than **5–10% of total prediction market capital to any single arb trade**. As your execution win rate climbs above 85%, you can increase to 15–20% per trade. Also be aware that running high-frequency arb strategies may have regulatory implications depending on your jurisdiction, especially as platforms like Kalshi operate under CFTC oversight. For a forward-looking perspective on regulatory context, the [deep dive on Polymarket trading after the 2026 midterms](/blog/deep-dive-polymarket-trading-after-the-2026-midterms) provides useful context on how the regulatory environment is evolving. --- ## Frequently Asked Questions ## What is the minimum price gap needed for cross-platform prediction arbitrage? A gross price gap of at least **5–8 cents per share** is generally the minimum worth pursuing, depending on total fee load across both platforms. After accounting for maker/taker fees (typically 2–4% combined), gaps smaller than this result in near-zero or negative net edge when execution slippage is factored in. ## Do limit orders guarantee a fill in prediction markets? No — limit orders guarantee a **price floor or ceiling**, not execution. In low-liquidity markets, a limit order may sit unfilled for hours or never fill at all. Always check order book depth before posting, and have a cancellation plan ready if one leg fills without the other. ## Can I automate cross-platform prediction arbitrage legally? Yes, in most cases. Polymarket and Kalshi both offer public APIs intended for programmatic trading. However, you should review each platform's terms of service for any restrictions on bot activity, and ensure your trading activity complies with applicable financial regulations in your jurisdiction. [PredictEngine](/) is designed to support compliant automated trading strategies. ## How much capital do I need to start cross-platform prediction arbitrage? You can technically start with as little as **$500–$1,000** split across two platforms, but practical arb requires enough capital to post meaningful position sizes on both legs simultaneously. Most active arb traders start with $5,000–$10,000 to ensure they can take positions large enough to generate worthwhile absolute returns while maintaining diversification across multiple open trades. ## What happens if one leg of my arbitrage trade fills but the other doesn't? This is called a **partial fill** or **leg mismatch**. At that point you have directional exposure rather than a hedged arb. You should either quickly cancel the unfilled leg and manage the filled position as a standalone trade, or hold both legs and wait to see if the second leg eventually fills — though prices may move against you during the wait. ## Are there tax implications specific to arbitrage trading in prediction markets? Yes. Each completed arb trade — even a small one — is generally a **realized taxable event** in the US and most other jurisdictions. Cross-platform arb generates a high volume of small gains that can be administratively complex. Using automated record-keeping from the start is strongly recommended. Review the [tax considerations for AI agents trading prediction markets](/blog/tax-considerations-for-ai-agents-trading-prediction-markets) for a detailed look at how arb income is typically treated. --- ## Start Executing Smarter Arb Trades Today Cross-platform prediction arbitrage with limit orders is one of the most systematic, repeatable edge strategies available to retail traders in prediction markets today. The barrier isn't intelligence — it's process discipline: verifying resolution criteria, calculating net edge properly, sizing to liquidity, and keeping clean records. Whether you're running trades manually or building toward full automation, [PredictEngine](/) gives you the infrastructure to monitor markets, post limit orders, and track performance across platforms — all in one place. Start with small positions, validate your process over 20–30 trades, and scale methodically. The edge is real; the execution is learnable.