PredictionToolkit logoPredictionToolkit
Language: English
Search tools
← Data APIs

Data API

predkit: normalized market data and resumable arbitrage streams

predkit exposes prediction-market metadata, prices, venue-dependent books, matched pairs and research alerts through a read-only API and resumable event stream.

3.5/ 5Editorial ratingEditorial assessment
Read the predkit API referencepredkit.ai
Available on
API · MCP
Availability: public

Screenshots and interface

Product preview1 / 2

The orders and execution reference, whose routes are marked planned.

What is predkit?

The API reference makes route status central to an integration. Live data covers market metadata, quotes, venue-dependent ladders, matched pairs, arbitrage signals, maker candidates and wallet rankings. Aggregated responses retain per-venue freshness or failure status, while depth classification distinguishes stored ladders, fetchable books, quote-only data and missing books. The ladder reference describes Kalshi as quote-only.

Account, balance, position, execution and Copilot API routes are planned. The reference explicitly says predkit does not place orders, despite paid automation and Copilot language on the pricing page. Only arbitrage and alerts SSE channels are live; quote, fill and position channels are planned. Historical pair alerts may remain after an edge disappears, so inspect the timestamped edge_now verdict and any gone or suppressed state rather than assuming a visible alert is current.

Who it is for

  • Developers building scanners across prediction venues.
  • Researchers checking whether paired contracts have equivalent settlement terms.
  • Market makers studying candidate capacity and available depth.

Features and coverage

  • Per-venue response status

    Identify stale or failed venues within aggregate results and handle their data separately.

  • Normalized metadata

    Read outcome definitions, timing and resolution-source fields across venues.

  • Depth classification

    Distinguish a stored ladder, a fetchable order book, a quote-only venue and a missing book.

  • Matched-market pairs

    Inspect equivalence confidence and the detector’s current verdict.

  • Edge measures

    Compare 3 gap measures: gross, executable and settlement-adjusted.

  • Structural detections

    Read mint/merge, categorical, conditional and time-decomposition alerts.

  • Resumable SSE

    The live arbitrage and alerts channels provide event IDs and replay for reconnecting clients.

  • Maker and wallet rankings

    Inspect candidate capacity, risk and copyability metrics as research inputs.

Workflows with predkit

Build a scanner

Read venue capabilities, fetch markets and retain venue status and timestamps with every quote.

Research a matched pair

Check resolution metadata, equivalence confidence and edge_now before comparing its legs.

Resume after disconnection

Persist the last event ID and use the documented replay or polling fallback when reconnecting.

Pricing and total cost

Published limits apply to the available data surface. Verify delivered features against live/planned status rather than inferring execution from paid-plan marketing.

Free

$0

  • Scanner alerts
  • Leaderboard view

Basic

$29/month

  • 100,000 API requests/month
  • 60 requests/minute
  • MCP

Advanced

$49/month

  • 1,000,000 API requests/month
  • 300 requests/minute

Pro

$99/month

  • 10,000,000 API requests/month
  • 1,000 requests/minute
  • Priority support

Fees and usage costs

  • Paid automation and Copilot claims conflict with planned API routes; verify the exact available surface before purchase.

Getting started

Before you start: Account, balance, position, execution and Copilot API routes are planned.

  1. Check live/planned status for each route you need.
  2. Obtain a bearer token.
  3. Inspect the per-venue capability map.
  4. Implement keyset pagination and per-venue degradation handling.
  5. Subscribe only to the currently live SSE channels.
  6. Retain detector timestamps and suppression reasons.

The reference explicitly says predkit does not place orders; execution routes remain planned.

Useful links

    What to check

    • Account, balance, position, execution and Copilot API routes are planned.
    • Only arbitrage and alerts SSE channels are live; quote, fill and position channels are planned.
    • A historical alert may stay visible after the current edge disappears.
    • The ladder reference describes Kalshi as quote-only.
    • Paid automation marketing does not override the API’s feature-status labels.

    A closer look

    Ratings & reviews

    Editorial rating
    3.5/ 5
    0 user reviews
    PredictionToolkit editorial

    Our take on predkit

    Normalized records, explicit venue freshness and resumable streams provide a useful read-only integration surface. Respect depth classifications and feature-status labels: order execution is not available.

    Based on documented features, setup and access terms. How we rate

    User reviews 0

    The main score switches to user ratings after 5 published reviews.

    Be the first to share your experience

    A specific example helps the next person choose the right tool.

    Related tools

    Browse category
    Adanos Polymarket stock-sentiment API and ticker-discovery entry
    Adanos Market Sentiment API
    Data API3.5Editorial

    Compare stock-related prediction activity with social and news sentiment using shared API access.

    • Access API · CLI

    Also in APIs and Data Providers.

    OrderbookTrade explanation of its execution and platform workflow
    OrderbookTraderestricted
    Infrastructure3.0Editorial

    Integrate order actions, matching and market-making tools through shared API and WebSocket infrastructure.

    • Access API

    Compare infrastructure focused on execution.

    Predictefy product overview
    Predictefy
    Data API3.0Editorial

    Normalized prediction-market data, matched contracts, replay and paper trading for multi-venue research.

    • Access Web · API · MCP

    Compare another normalized API spanning multiple venues.

    Frequently asked questions about predkit

    Can I execute orders through this API?

    No. The documented execution routes are planned, and the reference explicitly says no orders are placed.

    Which stream channels are live?

    Arbitrage and alerts. Quote, fill and position channels are planned.

    What does edge_now represent?

    The detector’s latest timestamped verdict, including states where the edge is gone or suppressed.

    How should a client handle a slow venue?

    Responses provide per-venue status so the client can degrade gracefully instead of treating every venue’s data as equally current.