Order-book backtesting
PolyTest Alternative for Polymarket Historical Data
Overview
Quick comparison
PolyTest facts from its public pages (verified September 24, 2026); PolyOrderbooks facts from our product docs.
| Feature | PolyTest | PolyOrderbooks |
|---|---|---|
| Historical prices | Yes — price and backtest history for covered BTC/ETH/SOL Up/Down markets | Yes |
| Historical L2 books | Yes — order-book depth in snapshot payloads, documented at 8 levels per snapshot | Yes — full bid/ask ladders |
| Capture / delivery | Self-reported sub-second snapshots (42 ms p50, p99 under 120 ms); timeframes 5m/15m/1hr/4hr/24hr | 250ms capture; 250ms query resolution on every plan, including free |
| REST API | Yes — REST API for historical snapshots and backtest execution | Yes |
| Python tooling | No official SDK; clean JSON responses are the documented integration path | Official Python SDK on PyPI |
| Bulk export | Bulk export API on Enterprise only; not on self-serve plans | Enterprise S3 delivery (Parquet, CSV, JSON) — not on self-serve plans |
| Free tier | 3-day free trial on Builder; no permanent free tier documented | Yes — Starter: 250ms L2, prices, and metrics at $0 (3-day history) |
| Starting paid price | Builder $29/mo or $17/mo billed annually ($204/yr) at 14 days history, 250 req/min, 3 API keys; Pro $49/mo or $29/mo annually ($348/yr) at full history, 750 req/min, 40 req/s burst, 10+ keys | $19/month Pro (public pricing at time of verification) |
| Coverage | BTC, ETH, SOL Up/Down markets; XRP, DOGE, BNB announced as coming soon | Polymarket crypto markets (Up/Down and related) — depth history, not metadata breadth |
| Historical coverage | Builder: 14 days of history. Pro: full historical data (both self-reported) | Continuous 250ms archive from 3-day Starter windows to 30–120-day paid windows; resolved markets stay queryable |
Source (PolyTest): https://polytest.io
Purpose-built for Up/Down backtesting
PolyTest targets one workload: replaying recorded order books for crypto Up/Down markets and testing strategies against them. Its docs model a snapshot per order-book state with timestamps to the millisecond, plus a timestamp lookup API, so backtests are defined against a captured book rather than a synthetic candle. Coverage today is BTC, ETH, and SOL Up/Down across 5m, 15m, 1hr, 4hr, and 24hr timeframes, with XRP, DOGE, and BNB displayed as coming soon. If your strategy lives in that exact slice, PolyTest is built directly for it — but its own pages put a hard 8-level cap on depth per snapshot, which is a real constraint for fill simulation on liquid rounds.
The trade-off is the envelope. Its own numbers are self-reported: 14 days of history on the Builder plan ($29/mo or $17/mo billed annually), full history on Pro ($49/mo or $29/mo annually), and sub-second latency claims (42 ms p50, p99 under 120 ms). There is no permanent free tier — a 3-day trial converts to Builder unless cancelled.
Three claims to pin down before you commit
Depth is capped at 8 levels. Both the live preview widget and PolyTest's own testimonial copy call out “8 levels” of depth per snapshot. For slip-heavy five-minute rounds with a near-certain winner, the full ladder is exactly what you need to reconstruct realistic fills — PolyOrderbooks stores the complete bid/ask ladder on every snapshot instead.
“Sub-second” is a latency figure, not a sampling grid. PolyTest's 42 ms p50 claim describes API response latency on top of captured snapshots. PolyOrderbooks captures every 250ms and offers 250ms query resolution on every plan including free — a uniform grid you can reason about, rather than a vendor-best-case round-trip time.
Uptime claims conflict across its own pages. The homepage advertises 99.9% uptime over the last 60 days, while the Pro plan lists a 99.5% uptime SLA. Ask for which number the plan you buy actually guarantees.
When PolyTest fits
Every item below is scoped to the covered BTC/ETH/SOL Up/Down subset — a smaller envelope than the ongoing archive described in the next section.
- Backtests scoped to Polymarket crypto Up/Down rounds on the three covered coins
- Timestamp-based strategy entries against captured snapshots
- Multi-timeframe tests across 5m, 15m, 1hr, 4hr, and 24hr buckets
- Higher burst throughput for real-time pipelines (Pro allows 40 req/s bursts)
- A 3-day trial to validate responses before subscribing
When our archive fits instead
If your research spans markets beyond three crypto Up/Down coins — or you need the full ladder rather than 8 documented levels — PolyOrderbooks captures Polymarket crypto order books every 250ms and serves them over REST with 250ms query resolution on every plan. Resolved markets stay queryable, the schema is stable, and a free Starter tier plus a free BTC 5-minute L2 sample let you validate before paying.
PolyOrderbooks is also the provider in this comparison with an officially published MCP server and a Python SDK on PyPI, so the same archive works from Cursor, Claude Desktop, or your own scripts.
If you would rather describe the strategy than write the replay loop, Backtest AI tests a plain-English idea against the same archive and explains every run.
FAQ
What is PolyTest?
PolyTest (polytest.io) is a Polymarket backtesting API for crypto Up/Down markets. It replays recorded order books and lets you define and test trading strategies against them, with 8 levels of depth per snapshot, timestamp lookup, and self-reported sub-second latency (42 ms p50, p99 under 120 ms). Coverage is BTC, ETH, and SOL, with XRP, DOGE, and BNB announced as coming soon.
Does PolyTest have historical Polymarket order books?
Yes, for the Up/Down markets it covers. It stores order book depth in each snapshot (documented at 8 levels per payload) with price, size, volume, and millisecond timestamps served over REST. History windows are self-reported: 14 days on Builder, full history on Pro. Builder is $29/mo or $17/mo billed annually ($204/yr); Pro is $49/mo or $29/mo annually ($348/yr).
PolyTest vs PolyOrderbooks — which should I use for backtesting?
PolyTest is built specifically for BTC/ETH/SOL Up/Down backtesting, with sub-second latency claims and a documented 8-level depth cap. PolyOrderbooks archives Polymarket crypto markets more broadly at uniform 250ms capture with 250ms REST query resolution on every plan, keeps resolved markets queryable, and adds full-ladder depth, an official Python SDK, and an official MCP server. Use PolyTest for its fine Up/Down focus; use PolyOrderbooks when you want broader market coverage, full ladder depth, or MCP/AI-tooling integration.
What are PolyTest alternatives?
PolyOrderbooks for broader ongoing Polymarket crypto L2 over REST with an official MCP server; PolyBackTest for BTC/ETH full-depth backtesting archives; DepthFeed for event-driven full-depth capture across venues; Telonex for tick-level Parquet pipelines.
How do I validate PolyTest data before porting a backtest pipeline?
The same check applies to any provider: ask for a sample and verify a real order book never has a bid at or above the best ask. Run that test on PolyTest's 3-day free trial, and run it on our free BTC 5-minute L2 sample too, so you can compare schemas, timestamp formats, and the 8-level depth cap against a full-ladder archive before rewriting any parser.