What is predkit?
predkit’s API reference separates live routes from planned ones. The live surface covers market metadata, quotes, venue-dependent ladders, matched pairs, arbitrage signals, maker candidates and wallet rankings. Account reads, order execution and Copilot API routes are marked planned, despite broader automation language on the pricing page.
Who it is for
- Developers building multi-venue scanners
- Researchers comparing settlement-equivalent pairs
- Market makers evaluating candidate pools and depth
Features and coverage
- Available on
- REST API, SSE, MCP
- Markets & venues
- Multiple prediction venues
- Research topics
- Matched markets, Structural arbitrage
- Per-venue status
Aggregated responses identify stale or failed venues.
- Normalized metadata
Read outcome, timing and resolution-source fields.
- Depth classification
Distinguish a stored ladder, fetchable book, quote-only venue or missing book.
- Matched pairs
Inspect equivalence confidence and current detector verdict.
- Three edge measures
Compare gross, executable and settlement-adjusted gaps.
- Structural alerts
Read mint/merge, categorical, conditional and time-decomposition detections.
- Resumable SSE
Live arbitrage and alerts channels support event IDs and replay.
- Maker and wallet rankings
Review candidate capacity, risk and copyability metrics.
Workflows with predkit
Build a scanner
Read venue capabilities, fetch markets, then retain status and timestamp fields with every quote.
Research a pair
Check its resolution metadata, equivalence confidence and edge_now verdict before comparing legs.
Resume a stream
Persist the last event ID and use the documented replay/poll fallback after disconnection.
Pricing and total cost
Published plan limits apply to the available data surface; confirm feature delivery against the API status labels.
Free
$0
- Scanner alerts
- Leaderboard view
Basic
$29/month
- 100K API requests/month
- 60 requests/minute
- MCP
Advanced
$49/month
- 1M API requests/month
- 300 requests/minute
Pro
$99/month
- 10M API requests/month
- 1,000 requests/minute
- Priority support
Fees and usage costs
- Paid automation and Copilot claims on the pricing page conflict with planned API labels; verify the exact surface before purchase.
Getting started
Before you start: The reference explicitly says predkit places no orders today.
- Read the live/planned status on each required route.
- Obtain a bearer token.
- Inspect the venue capability map.
- Implement keyset pagination and per-venue degradation.
- Subscribe only to the currently live SSE channels.
- Retain detector timestamps and suppression reasons.
Useful links
What to check
- The reference explicitly says predkit places no orders today.
- Account, balance, position and execution routes are planned.
- Only arbitrage and alerts SSE channels are live; quote/fill/position channels are planned.
- A pair’s historic alert can remain visible after the current edge has disappeared.
- Kalshi ladders are described as quote-only in the ladder reference.
A closer look
Ratings & reviews
User reviews 0
The main score switches to user ratings after 5 published reviews.
A specific example helps the next person choose the right tool.
Write a review
How was your experience with predkit?
Share what you used, what worked and what could be better. We confirm your email and review the submission before publishing.
To submit a review, email info@polytradingbot.com with the tool name, your rating and your experience. Enable JavaScript to prepare a draft here.
Related tools
Browse categoryFrequently asked questions about predkit
Can I execute orders through the documented API?
No. Execution routes are marked planned.
Which stream channels are live?
Arbitrage and alerts.
What does edge_now mean?
The detector’s latest timestamped verdict, including gone or suppressed states.
Can one slow venue fail the whole aggregate?
Responses include per-venue status so clients can degrade gracefully.


