You probably found Limitless Exchange because you were looking for “the next Polymarket.” Fair \u2014 that’s basically what it is, except it runs on Base (Coinbase’s L2) instead of Polygon, the fee structure is different, and the UX is built around binary “yes\/no” markets rather than multi-outcome events. If you’re building prediction-market tooling, ignoring Limitless at this point would be a mistake.<\/p>\n
Here’s the problem: like every onchain prediction market, Limitless’s “API” is really three things duct-taped together \u2014 a Gamma-style metadata service, an onchain smart contract you query via Base RPC, and a CLOB-style order book living at the edge of it all. You glue those together yourself.<\/p>\n For read-only price data \u2014 the part 90% of devs actually want \u2014 this is overkill.<\/p>\n OddsPapi aggregates 350+ venues, including Limitless Exchange, under one API key. You don’t need a Base RPC, you don’t need to resolve condition IDs, and you don’t need to convert share prices to decimal odds. You query Limitless Exchange is an onchain prediction market running on Base. Each market is a binary question \u2014 “Will X happen by date Y?” \u2014 and resolves to yes or no. Share prices trade between 0 and 1, where the price is the market’s implied probability of “yes”: a share trading at 0.62 means the market collectively thinks there’s a 62% chance.<\/p>\n That probability is the interesting number. For a developer comparing Limitless to a sportsbook, you want it as decimal odds<\/strong>, not a raw share price. The conversion is simple \u2014 Sportsbooks bake in vig (typically 4\u20138%). Onchain binary markets like Limitless don’t \u2014 their “vig” is the bid\/ask spread on the shares themselves, which is often tighter than the sportsbook margin on major events. Any time the implied probability on Limitless disagrees meaningfully with the no-vig sharp line from Pinnacle, you’ve either found an arbitrage or a market that believes something the book doesn’t.<\/p>\n Limitless markets route through the same Two things:<\/p>\n Coverage note:<\/strong> Limitless’s sports coverage through OddsPapi is currently focused on major fixtures where there’s onchain liquidity \u2014 political markets, crypto-native events, and headline NBA\/MLB\/NFL games. Niche fixtures will return an empty book. This is the same pattern as Polymarket’s sports coverage: deep on a small set of markets, absent on the long tail.<\/p>\n<\/blockquote>\n Limitless leans US-sports and headline events. Start with NBA ( The actual use case: Limitless says 62%, Pinnacle’s no-vig fair line says 58%. Which is right? Here’s how you grab both in one request and start answering that question.<\/p>\n Run this on a hot fixture during market hours and you’ll see exactly how far onchain prediction markets drift from sharp sportsbook lines. That drift is the whole game for prediction-market traders.<\/p>\n No Base RPC<\/strong> \u2014 You don’t maintain a Web3 provider, you don’t handle reorg edge cases, you don’t pay gas to read.<\/p>\n Already decoded<\/strong> \u2014 Share prices are already decimal odds. Condition IDs and token IDs are still available in One request, every venue<\/strong> \u2014 Limitless + Polymarket + Kalshi + Pinnacle + Betfair Exchange, side by side. That’s the whole prediction-market stack in a single call.<\/p>\n Free historical data<\/strong> \u2014 \n\n
\n \nRequirement<\/th>\n Reality<\/th>\n<\/tr>\n<\/thead>\n \n Network<\/strong><\/td>\n Base L2 (Coinbase rollup on Ethereum)<\/td>\n<\/tr>\n \n Market Format<\/strong><\/td>\n Binary (yes\/no) outcomes, conditional tokens<\/td>\n<\/tr>\n \n Market IDs<\/strong><\/td>\n Onchain condition IDs + token IDs per outcome<\/td>\n<\/tr>\n \n Prices<\/strong><\/td>\n Share price (0\u20131), reads as implied probability \u2014 you convert to decimal odds yourself<\/td>\n<\/tr>\n \n Metadata<\/strong><\/td>\n Off-chain API, paginated, separate from prices<\/td>\n<\/tr>\n \n Trading<\/strong><\/td>\n EIP-712 signed orders against a Base-deployed contract<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/figure>\n The “Third Option” for Limitless Exchange Odds<\/h2>\n
?bookmakers=limitless-ex<\/code> on a fixture and get decimal-formatted prices with the same back\/lay\/exchange shape every other exchange uses on OddsPapi.<\/p>\n\n\n
\n \nFeature<\/th>\n Limitless Direct<\/th>\n OddsPapi<\/th>\n<\/tr>\n<\/thead>\n \n Auth<\/strong><\/td>\n EIP-712 + Base wallet<\/td>\n Single API key<\/td>\n<\/tr>\n \n Wallet<\/strong><\/td>\n Required<\/td>\n Not needed for reads<\/td>\n<\/tr>\n \n Odds Format<\/strong><\/td>\n Share price (0\u20131)<\/td>\n Decimal, ready to use<\/td>\n<\/tr>\n \n Metadata Lookups<\/strong><\/td>\n Second off-chain API<\/td>\n Same response as prices<\/td>\n<\/tr>\n \n Compare vs Sportsbooks<\/strong><\/td>\n Separate integration per book<\/td>\n One request, all books<\/td>\n<\/tr>\n \n Historical Data<\/strong><\/td>\n Query onchain event logs yourself<\/td>\n Free on entry tier<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/figure>\n What Limitless Actually Is<\/h2>\n
decimal = 1 \/ share_price<\/code> \u2014 but you have to remember to do it on every single query, and if you forget, your arbitrage model is silently wrong. OddsPapi does the conversion on ingestion so every limitless-ex<\/code> price you see is already in decimal.<\/p>\nWhy Pull Limitless Alongside a Sportsbook<\/h3>\n
The JSON Shape<\/h2>\n
\/v4\/odds<\/code> endpoint as every other bookmaker. The outcome block sits under bookmakerOdds.limitless-ex<\/code>, and the structure mirrors the exchange-type shape used by Polymarket, Kalshi, and SX Bet. Main price lives on the price<\/code> field, the lay (opposite) side is exposed via exchangeMeta<\/code>:<\/p>\n# Limitless-style exchange outcome (structure shared with Polymarket\/Kalshi)\n{\n \"active\": true,\n \"betslip\": \"https:\/\/limitless.exchange\/markets\/0x...\",\n \"bookmakerOutcomeId\": \"0x...\", # Base condition\/token id\n \"changedAt\": \"2026-04-11T09:38:17+00:00\",\n \"limit\": null,\n \"price\": 1.613, # decimal odds (already converted)\n \"exchangeMeta\": {\n \"lay\": 2.631, # lay \/ \"no\" side in decimal\n \"bookmakerLayOutcomeId\": \"0x...\"\n }\n}<\/code><\/pre>\n\n
price<\/code><\/strong> is the “yes” side in decimal. If you want implied probability, divide 1 by it: 1 \/ 1.613 = 0.62<\/code>, i.e. the market thinks “yes” is 62%.<\/li>\nexchangeMeta.lay<\/code><\/strong> is the “no” side of the same market in decimal odds. Back + lay together give you the full round trip \u2014 this is the data you need for arbitrage.<\/li>\n<\/ul>\n\n
Tutorial: Pull Limitless Exchange Odds in Python<\/h2>\n
Step 1: Grab Your API Key<\/h3>\n
import requests\n\nAPI_KEY = \"YOUR_API_KEY\"\nBASE_URL = \"https:\/\/api.oddspapi.io\/v4\"<\/code><\/pre>\nStep 2: Discover a Fixture<\/h3>\n
sportId=11<\/code>) or NFL (14<\/code>) \u2014 whichever is in season.<\/p>\nfrom datetime import datetime, timezone, timedelta\n\ntoday = datetime.now(timezone.utc)\nparams = {\n \"apiKey\": API_KEY,\n \"sportId\": 11, # NBA\n \"from\": today.strftime(\"%Y-%m-%d\"),\n \"to\": (today + timedelta(days=3)).strftime(\"%Y-%m-%d\"),\n}\nfixtures = requests.get(f\"{BASE_URL}\/fixtures\", params=params).json()\ncandidates = [f for f in fixtures if f.get(\"hasOdds\")]<\/code><\/pre>\nStep 3: Query Limitless<\/h3>\n
fixture_id = candidates[0][\"fixtureId\"]\n\nr = requests.get(\n f\"{BASE_URL}\/odds\",\n params={\n \"apiKey\": API_KEY,\n \"fixtureId\": fixture_id,\n \"bookmakers\": \"limitless-ex\",\n },\n)\ndata = r.json()\n\nlimitless = data.get(\"bookmakerOdds\", {}).get(\"limitless-ex\")\nif not limitless:\n print(\"No Limitless market on this fixture \u2014 try a headline game.\")\nelse:\n print(f\"{len(limitless['markets'])} markets from Limitless\")<\/code><\/pre>\nStep 4: Parse Yes \/ No as Decimal Odds<\/h3>\n
# Market 101 = Full Time Result \/ Moneyline\nmarket = limitless[\"markets\"][\"101\"]\n\nfor outcome_id, outcome in market[\"outcomes\"].items():\n p = outcome[\"players\"][\"0\"]\n if not p[\"active\"]:\n continue\n\n yes_decimal = p[\"price\"]\n yes_prob = 1 \/ yes_decimal\n\n meta = p.get(\"exchangeMeta\") or {}\n no_decimal = meta.get(\"lay\") if isinstance(meta, dict) else None\n\n print(f\"outcome {outcome_id}: yes @ {yes_decimal} ({yes_prob:.1%}) | no @ {no_decimal}\")<\/code><\/pre>\nStep 5: Implied Probability vs Sportsbook No-Vig<\/h3>\n
r = requests.get(\n f\"{BASE_URL}\/odds\",\n params={\n \"apiKey\": API_KEY,\n \"fixtureId\": fixture_id,\n \"bookmakers\": \"limitless-ex,pinnacle\",\n },\n)\nbooks = r.json()[\"bookmakerOdds\"]\n\ndef implied(decimal):\n return 1 \/ decimal if decimal else None\n\nfor slug in (\"limitless-ex\", \"pinnacle\"):\n book = books.get(slug, {})\n m = book.get(\"markets\", {}).get(\"101\", {})\n home = m.get(\"outcomes\", {}).get(\"101\", {}).get(\"players\", {}).get(\"0\", {})\n price = home.get(\"price\")\n print(f\"{slug:13} home @ {price} ({implied(price):.1%})\" if price else f\"{slug:13} none\")<\/code><\/pre>\nWhy Devs Pick OddsPapi Over a Direct Base Integration<\/h2>\n
bookmakerOutcomeId<\/code> if you want them, but the conversion work is done.<\/p>\n\/v4\/historical-odds?fixtureId=\u2026&bookmakers=limitless-ex<\/code> gives you the full price history without writing event-log subgraphs.<\/p>\nGet Started<\/h2>\n