Skip to content

Learn

Build with matched Kalshi and Polymarket data

Task-based guides for the Dino API and MCP server. Each tutorial starts from a free key and ends with a working result.

Start

Monitor Kalshi and Polymarket with Python

Build a Python monitor for matched Kalshi and Polymarket markets, then extend the delayed REST snapshot with real-time updates.

You will print a ranked table of current cross-venue gaps from a free REST key.

Start

Kalshi + Polymarket MCP for Claude and Cursor

Connect Claude or Cursor to Dino's Kalshi and Polymarket MCP server and inspect matched markets with settlement context.

You will give Claude or Cursor a matched-market research tool through MCP.

Understand

Compare Kalshi and Polymarket safely

Compare Kalshi and Polymarket contracts with settlement risks and contract differences attached to every observed price.

You will inspect outcome and settlement differences before comparing two venue prices.

Build

A live feed of cross-venue price gaps, no server required

The REST snapshot runs about two minutes behind, long after a nine-second gap has already closed. Here's how to watch one open in real time from a single HTML file, no server involved.

You will open a live cross-venue price viewer from one local HTML file.

Build

Where to run your 24/7 stream consumer, and how to keep it alive

Where to host a stream consumer that runs continuously: a Mac mini already on the desk, a cheap VPS, or a serverless option like Cloudflare Durable Objects, and how to keep each one alive across reboots and crashes.

You will keep a stream consumer alive through disconnects and restarts.

Build

Send a Telegram alert the moment a cross-venue price gap opens

A qualifying gap can close before you've refreshed a tab. Here's how to subscribe to the matched feed and alert on the moments the server confirms a real arb, then push each one to Telegram before it's gone.

You will send one debounced Telegram alert when a confirmed gap clears your threshold.

Need the field reference? Read the API documentation. Want the underlying research? Browse the Dino blog.