# Predictefy

Sixteen venues behind one verb family, priced in credits, with nothing readable for free.

*https://predictionmarkets.tools/tools/predictefy · Prediction Market Data APIs*

## Facts

### At a glance

| Field | Value |
| --- | --- |
| Vendor | Predictefy |
| Category | Prediction Market Data APIs |
| Job | cross_venue_feed |
| Website | https://predictefy.com |
| Pricing model | usage |
| Free tier | true |
| Open source | false |
| Licence | none |
| Self-hosted | false |
| Tested hands-on | false |
| Last updated | 2026-09-19 |

### Pricing

| Tier | USD | Period |
| --- | --- | --- |
| Free | 0 USD | — |
| Builder | 49 USD | — |
| Pro | 249 USD | — |
| Scale | 999 USD | — |
| Enterprise | 2500 USD | — |

### Availability

| Field | Value |
| --- | --- |
| Jurisdictions | global |
| Open to US persons | true |
| KYC required | false |

### Markets

| Field | Value |
| --- | --- |
| Subjects | politics, sports, macro, crypto |
| Settlement | cash |
| Resolved by | none |

### Economics

| Field | Value |
| --- | --- |
| Taker fee | none |
| Maker fee | none |
| Liquidity model | clob |
| Platforms | library |
| AI features | assistive |

### Interfaces

| Field | Value |
| --- | --- |
| API | true |
| WebSocket | true |
| Scripting | none |
| Python | true |
| MCP server | true |
| Export | json |

### Capabilities

Yes: order_book, automation, live_trading, paper_trading, portfolio_tracking, cross_venue

No: charting, screening, backtesting, calibration_scoring, alerts, news, tax_reporting

*Verified: pricing 2026-09-19; availability 2026-09-19.*

## What it is

The broadest unified layer in this category, and the one that most directly occupies the hole
Dome left. One key, one response envelope, and a verb family borrowed from crypto exchange
clients — `fetchMarkets`, `fetchOrderBook`, `fetchTrades`, `fetchOHLCV`, `has` — addressed as
`/api/{exchange}/{verb}` on `data.predictefy.com`, with a `router` pseudo-venue that unions the
list verbs across every served venue at once.

The documentation lists sixteen venue ids: `polymarket`, `kalshi`, `opinion`, `hyperliquid`,
`limitless`, `polymarket_us`, `sxbet`, `myriad`, `gemini`, `rain`, `predictfun`, `pascal`, `xo`,
`pred`, `predictstreet` and `novig`.

Around the reads sit four more surfaces: a WebSocket that sends full book snapshots rather than
deltas, a cross-venue cluster and discrepancy layer, a non-custodial execution service on a
separate origin, and funding and bridge helpers that build unsigned transactions. There is also a
`/v1/sql` analytical endpoint that no self-serve plan grants.

What distinguishes the documentation from its neighbours is a stated posture about honesty in the
data itself. Every record carries `asOf`, a `provenance.source`, and a per-venue `capabilities`
object; an unsupported venue-and-verb pair answers `NOT_SUPPORTED` rather than an empty array; a
reconstructed one-level book is flagged `synthetic: true`; `page.total` can be `null` meaning *not
counted*, never *zero*; and candles carry `quality` and `isTrueCandle` so a derived bar is
distinguishable from a real one. Whether the data is good is not something this card can tell you.
Whether the vendor has thought about how data goes wrong is visible from outside, and it has.

## Availability

No geographic gate and no identity check: an account is an email address, sign-up is free and
needs no invite, and the API is bought with a card. The operating entity named in the site footer
is Predictefy Inc.

What is gated is everything else. An unauthenticated request to the markets endpoint answered
`401 UNAUTHORIZED` on 19 September 2026, and `data.predictefy.com/health` answered 200 with a
status object — the service is live and closed, which is all an outside check can establish.

Two contractual limits sit on the free plan and are easy to miss in the table: **commercial use is
not permitted on it**, and extra credits cannot be bought on it at all. The plan a reader evaluates
with is not a plan they can ship on.

## Pricing

Two products, priced separately. This card is the API and SDK, which are metered in credits on
five plans; the vendor also sells a separate cross-venue arbitrage terminal as a flat subscription
at 48.88 USD a month, described on the pricing page as covering eight venues.

The API plans are Free at 0 USD with 25,000 credits a month, Builder at 49, Pro at 249, Scale at
999, and Enterprise from 2,500 by contract. What escalates is credits, requests a minute, API
keys, streaming connections and the history window — 7 days on Free, 12 months on Builder,
unlimited from Pro up. Pro carries a three-day trial.

Credits are charged by weight rather than by request: 1 for metadata, search or a price snapshot,
2 for trades or candles, 5 for an order-book snapshot, a history query, an existing cross-match
lookup or an order submission, 10 for a cross-venue comparison, a price-gap query or smart-money
analytics, 15 for an arbitrage query, and 25 for a fresh AI-assisted cross-match. Bulk requests
cost the base weight times the number of hundred items returned. Streaming is 2 credits per
connection-minute, prepaid.

One line in the meter is worth reading twice, because it is a factor of four hundred: a
connection-minute holding a Polymarket **pending-fills** subscription costs 800 credits instead of
2. On the Free plan's 25,000 credits, that is about half an hour of it.

The API section of the pricing page is labelled a private beta, and the SDK and MCP packages are
published on beta version lines.

## Markets & resolution

Whatever the sixteen venues list, which the vendor groups as regulated exchanges, on-chain
venues, an on-chain perpetuals venue and several newer books. Predictefy resolves nothing and
settles nothing, so `resolution_source` on this card is null and every settlement question belongs
to the venue that wrote the rules. The `settlement` field says `cash` for the regulated majority
and should be read as a property of the underlying venues, not of the feed — a normalized price
from a play-money venue is not a price anyone can be paid at.

Coverage is documented per capability rather than claimed in a lump, which is the useful part.
The docs name which venues serve real CLOB depth and which return a synthetic top-of-book, which
publish a public trade tape and which answer `501 NOT_SUPPORTED` instead of synthesizing one, and
which eleven have proven stored history against five that report `history: false`. They also warn
that three venues can return write-forward derived candles that are not true venue candles.

The cross-venue layer is the part that replaces what nobody else publishes. `/v1/clusters` matches
equivalent markets across venues, with a `similarity` score the documentation explicitly refuses
to call a calibrated probability of equivalence, and `/v1/discrepancies` reports mid-price gaps
between cluster members. The arbitrage endpoint applies a set of gates — live non-synthetic asks
on both legs, open status, full depth at the requested size, a verified per-venue fee model,
resolution equivalence, positive net edge — and everything that fails one is labelled an
indicative price discrepancy with a machine-readable reason.

## Integrations

REST, WebSocket, MCP and two SDKs. The TypeScript client is `@predictefy/sdk` on npm, MIT, at
1.0.0-beta.9 published 19 September 2026 from the vendor's own `Predictefy/predictefy-core`
repository; the Python client is `predictefy` on PyPI, MIT, at 1.0.0b7 the same day. There is also
`@predictefy/cli` and `@predictefy/mcp`. All four are on beta lines, and the documentation itself
says to pin an exact version rather than track `latest`.

The MCP server runs with `npx -y @predictefy/mcp` and exposes 42 tools by default — 33 read,
intelligence and platform tools plus 9 paper-trading tools for simulated orders — with a further
10 execution and collateral tools off unless `MCP_ENABLE_TRADE` is set. No single tool both builds
and submits an order.

Execution is deliberately separate: a different origin with no implicit default, an explicit opt-in
in the SDK, and a build-sign-submit split where the signing happens in your process. Spend caps
default to 100 USD per order and 1,000 USD per key per rolling 24 hours, every write needs an
`Idempotency-Key`, and new keys are read-only until a `trade` scope is added.

## Limitations

- **Nothing is readable without an account.** There is no demo endpoint, no delayed public tier and
  no sample payload behind a URL, so none of the coverage below can be checked before signing up.
  This card's venue counts are the vendor's claims.
- **The free plan cannot be used commercially**, and cannot buy extra credits. Its history window
  is seven days.
- **Two venue counts on the vendor's own site.** The docs describe sixteen served venue ids for
  the API; the pricing page describes the arbitrage terminal as covering eight. They are different
  products, but a reader comparing the two pages will not be told that.
- **Everything is beta.** The API pricing is labelled a private beta and all four client packages
  are on `1.0.0-beta` lines.
- **Credits make cost a function of your loop.** A one-second poller is 86,400 requests a day, and
  an order-book snapshot is five credits apiece.
- **`fetchTrades` is a snapshot, not a time-ranged query**, and `fetchOHLCV` is venue-scoped —
  `router` does not support it.
- **No withdrawal and no bridge-out.** Funds leave a venue only by that venue's own rails; nothing
  moves between venues through Predictefy, which the documentation states as a posture rather than
  a gap.

## Alternatives

[FinFeedAPI](https://predictionmarkets.tools/tools/finfeedapi) covers nine venues in one schema, sells usage credits with no
recurring free allowance, and ships historical flat files for order-book replay.
[Adjacent](https://predictionmarkets.tools/tools/adjacent) covers two venues and adds indices, reference rates and news on a seat
subscription with a delayed free tier. For the order-book history specifically,
[DepthFeed](https://predictionmarkets.tools/tools/depthfeed) and [Predexon](https://predictionmarkets.tools/tools/predexon) are the archive specialists.
[CCXT](https://predictionmarkets.tools/tools/ccxt) is the same unified-verb idea under an MIT licence, where you maintain the
normalisation instead of renting it. Dome, the previous unified API over Polymarket and Kalshi,
was acquired by Polymarket and its documentation set end of life for all Dome APIs at
28 April 2026.

## FAQ

### Can I try the Predictefy API without signing up?

No. Every data route answers 401 UNAUTHORIZED without a key — verified on 19 September 2026 against the markets endpoint. Only the health check is open, and it returns a status object rather than market data. Sign-up is free and needs no invite, and a new account starts with 25,000 credits a month.

### How many venues does Predictefy actually cover?

The documentation lists sixteen venue ids plus a router pseudo-venue, and says explicitly which of them have real order-book depth, a public trade tape and stored history. The vendor's own pricing page describes the separate arbitrage terminal as covering eight. Neither number could be checked from outside, because reading anything needs a key.

### What does a request cost?

Credits by weight — 1 for metadata, search or a price snapshot, 2 for trades or candles, 5 for an order-book snapshot, a history query or an order action, 10 for a cross-venue comparison or smart-money analytics, 15 for an arbitrage query and 25 for a fresh AI cross-match. Streaming is 2 credits per connection-minute.

### Does Predictefy hold my funds or my keys?

No, and the documentation is emphatic about it. Execution builds an unsigned artifact that your own signer signs in your process; there is no server-side signing route by design, no custody, and no route that moves a balance between venues or withdraws one.

### Is a cross-venue price gap an arbitrage?

Predictefy's own documentation says not by default. A row is only labelled executable when live non-synthetic asks, full depth at the requested size, open market status, a verified fee model and resolution equivalence all pass; everything else stays an indicative price discrepancy with a machine-readable reason.

## Background

- [Where your key lives when software trades for you](https://predictionmarkets.tools/guides/where-your-key-lives.md) — Four different credentials are all called a key, and they differ in what a copy permits. What the clients in this catalogue ask for, and what to ask them back.

- [Where weather data comes from and what you may do with it](https://predictionmarkets.tools/guides/where-weather-data-comes-from.md) — Observations, model output and archives are three products with three licences. The forecast is the cheap half; a clean observation history is not.

- [Why the same contract costs two different prices on two venues](https://predictionmarkets.tools/guides/why-the-same-contract-costs-two-prices.md) — Two venues quoting one outcome are quoting two contracts. What the gap between the prices is made of - rules, fallbacks, fees, collateral, exits, eligibility.

## Also worth comparing

- [Adjacent](https://predictionmarkets.tools/tools/adjacent.md) — Prediction-market indices and reference rates, with Kalshi on the tier you can test.
- [Apify prediction-market scrapers](https://predictionmarkets.tools/tools/apify-prediction-market-scrapers.md) — A store of third-party actors that normalize Kalshi and Polymarket into one row shape.
- [FinFeedAPI Prediction Markets API](https://predictionmarkets.tools/tools/finfeedapi.md) — Nine event venues normalized into one REST schema, billed by usage credit.
- [Kalshi API](https://predictionmarkets.tools/tools/kalshi-api.md) — REST, WebSocket and FIX access to a CFTC-regulated event exchange.
- [Polymarket US API](https://predictionmarkets.tools/tools/polymarket-us-api.md) — A keyless public gateway for reading, and a signed key behind KYC for trading.
- [DepthFeed](https://predictionmarkets.tools/tools/depthfeed.md) — The recorded bid-ask ladder for crypto up-or-down markets, which no venue keeps itself.

## Named as a replacement for

- [Metaforecast](https://predictionmarkets.tools/alternatives/metaforecast.md)