What is Predictefy?

Prices, outcomes, books, volume and liquidity share a normalized schema. Matched contracts and the arbitrage workspace help users inspect gaps together with size, venue and route context; paid history and replay support strategy research before comparison with paper behavior.

The pricing page publishes concrete plans, but landing-page API waitlist language conflicts with available-now wording. Confirm the needed surface in the portal. Monthly credits meter usage separately from request-rate bursts; reading a venue does not establish that all its trading actions are supported.

Who it is for

For developers building applications across venues and researchers comparing equivalent outcome contracts.
For teams that need historical replay and simulated orders before choosing a live execution route.

Features and coverage

Match and compare contracts
Compare related outcomes with normalized prices, volume, liquidity and books, then inspect spread, available size and route context in the arbitrage workspace.
Replay and paper orders
Paid plans provide history for replay research. Paper open-order limits depend on the plan, and Pro lists up to 25 armed conditional orders.
Developer and agent interfaces
API and SDK reduce the need to maintain separate venue adapters. The provider also documents MCP and CLI integration paths for agents.

Workflows with Predictefy

Budget a prototype

Start with Free metadata and price reads, then estimate weighted credits for metadata, books and comparisons before upgrading.

Validate a price gap

Check settlement terms, fees, available size and quote freshness on both legs before treating matched contracts as an executable opportunity.

Compare replay with paper behavior

Choose a history window, simulate orders and compare the result with current paper trading before selecting a supported live route.

Pricing and total cost

Monthly credit allowances and request-rate limits apply separately. Enterprise uses contractual limits and infrastructure.

Free

25,000 credits/month; 60 requests/minute
1 key, 2 streams, 7-day history and 10 paper orders

Builder

$48.88/month

500,000 monthly credits; 300 requests/minute
3 keys, 20 streams and 12-month history
Replay and arbitrage access

Pro

$149/month

5 million monthly credits; 3,000 requests/minute
10 keys, 100 streams, unlimited history window and 25 armed conditional orders

Enterprise

Custom

Contractual limits and infrastructure

Fees and usage costs

Annual billing advertises 20% savings. Builder top-ups cost $11 per 100K credits; Pro top-ups cost $5.50 per 100K. Purchased credits do not expire.

Getting started

Before you start: Monthly plan credits reset while purchased credits persist. Exhausted credits return 402 for metered calls; the FAQ says existing streams remain connected.

Read endpoint coverage and venue capabilities, then create a free portal account and API key.
Estimate credit usage and start with data reads or paper orders.
Confirm commercial licence terms before using the service in a customer-facing application.

Confirm actual portal access because the landing-page waitlist and available-now pricing messages differ.

Useful links

What to check

Monthly plan credits reset while purchased credits persist. Exhausted credits return 402 for metered calls; the FAQ says existing streams remain connected.
A shared schema and market match do not make settlement terms identical or execution available for every venue action.

A closer look

Ratings & reviews

Editorial rating

3.0/ 5

0 user reviews

PredictionToolkit editorial

Our take on Predictefy

Normalization, replay and agent interfaces make this a broad developer offering. Conflicting access messages reduce clarity, and budgets must account for both weighted credits and request-rate limits.

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