docs/articles/part3_arbitrage.md

# ArbIntel Part 3: Exploiting Cross-Platform Arbitrage

The holy grail of quantitative trading is arbitrage—the simultaneous purchase and sale of an asset to profit from an imbalance in the price. 

Because prediction markets are currently fragmented, with heavy US regulatory restrictions forcing Kalshi to operate differently than Polymarket, liquidity is isolated. Where liquidity is isolated, prices decouple.

## The Anatomy of an Arb Trade

Consider the market: *"Will the Federal Reserve cut rates by 25bps in September?"*

Let's assume the current order books look like this:
*   **Polymarket**: Bid \$0.50 | Ask \$0.52
*   **Kalshi**: Bid \$0.55 | Ask \$0.57

The inefficiency is screaming at us. ArbIntel detects this instantly via its WebSocket listeners.
1.  **The Buy**: We buy the "YES" contract on Polymarket at the Ask price of \$0.52.
2.  **The Sell**: We simultaneously sell the "YES" contract (or buy "NO") on Kalshi at the Bid price of \$0.55.

Our gross margin is $0.55 - 0.52 = \$0.03$ per contract (a 3% risk-free return). 

## Overcoming Edge Friction

Gross margin is vanity; net margin is sanity. ArbIntel's `CrossPlatformArbitrage` module calculates true edge by accounting for two major frictions:

1.  **Fees**: Polymarket historically has 0% taker fees, but interacting with the Polygon blockchain incurs gas costs. Kalshi utilizes a sliding fee schedule capped at a certain dollar amount. The scanner deducts the estimated fees from the gross margin dynamically before executing.
2.  **Slippage & Depth**: We cannot arb 10,000 contracts if the Kalshi bid size is only 500 contracts. The module computes the maximum executable size as `min(Polymarket_Ask_Size, Kalshi_Bid_Size)`. 

If the net margin after fees remains above our predefined risk-free threshold (e.g., 0.5%), ArbIntel fires off simultaneous Execution API requests. 

In the final post, **Part 4**, we'll explore how ArbIntel uses Hugging Face NLP to trade breaking news momentum before human traders can react.