PredictionToolkit logoPredictionToolkit
Language: English
Search tools
← Historical data

Dataset

OutcomeTick: crypto Up/Down tick archives and replay data

OutcomeTick archives supported Polymarket and Predict.fun crypto Up/Down markets for downloadable historical research and replay.

4.0/ 5Editorial ratingEditorial assessment
Explore OutcomeTick archives and samplesoutcometick.com
Available on
API · Downloads · SDK
Availability: public

Screenshots and interface

Product preview1 / 1

Provider presentation of historical coverage and replay tooling.

What is OutcomeTick?

The archive includes settlement feeds, order-book records and supported trade prints, with market settlement metadata and per-file integrity information. Separate event and receive timestamps help reconstruct what happened and when the collector could observe it; documented missing intervals remain visible instead of being silently treated as complete data.

Coverage starts June 8, 2026 and is limited to the listed assets, intervals, streams and dates, with documented stream changes and gaps. This is not a history of every Polymarket question. The provider offers an SDK and hosted replay/backtests alongside downloads, but neither file integrity nor a replay result establishes a profitable strategy.

Who it is for

  • Quantitative researchers reconstructing crypto Up/Down market sequences.
  • Developers needing downloadable order-book and settlement history.

Features and coverage

  • Tick-level archives

    Retrieve supported settlement feeds, order-book records and trade prints for the selected crypto market coverage.

  • Provenance and file integrity

    Inspect event and receive times, documented gaps, byte lengths and SHA-256 checksums before using the files.

  • Replay and SDK tooling

    Use downloadable data with the SDK or evaluate the provider’s hosted replay/backtest service; completeness and results were not independently benchmarked.

Workflows with OutcomeTick

Establish dataset suitability

Inspect a public sample and confirm the required asset, interval, fields, stream coverage and dates.

Assemble a replay dataset

Download the selected files, verify checksums and keep event time separate from receive time and the later settlement information.

Pricing and total cost

Monthly access covers a rolling 30-day window: $10/month for one venue or $18/month for both. Older history is purchased separately. Hosted backtests start at $2, with charges based on work scanned.

One venue

$10/month

  • Rolling 30-day archive for one supported venue.

Both venues

$18/month

  • Rolling 30-day archive for Polymarket and Predict.fun.

Hosted backtests

From $2

  • Usage billing based on work scanned; older archive history is a separate purchase.

Access: Paid archive downloads require an API key. Public samples are available before purchase.

Getting started

Before you start: The archive starts June 8, 2026 and contains documented stream changes and gaps.

  1. Review sample schemas and documented stream coverage.
  2. Choose the venue coverage and date range required for the study.
  3. Obtain the necessary archive access, download selected files and verify their checksums before analysis.

An API key is required for paid archive downloads; public samples can be inspected before purchase.

Useful links

    What to check

    • The archive starts June 8, 2026 and contains documented stream changes and gaps.
    • Monthly plans include only the trailing 30 days; deeper history costs extra.
    • Coverage is limited to supported crypto assets, intervals and streams.
    • Completeness, collection latency and replay outputs were not independently benchmarked.
    • Integrity information does not demonstrate a profitable strategy.

    A closer look

    Ratings & reviews

    Editorial rating
    4.0/ 5
    0 user reviews
    PredictionToolkit editorial

    Our take on OutcomeTick

    Inspectable archive documentation and clear access prices make OutcomeTick a strong research candidate. Completeness, collection delay and replay results still require independent validation.

    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
    PolyTerm repository README describing the read-only terminal
    PolyTerm
    Learning & media4.0Editorial

    Follow a Polymarket market in a read-only terminal with explicit labels for data sources, freshness and resolution context.

    • Access CLI · Self-hosted

    Inspect a live order book separately from historical backtests.

    Convex Lake endpoints, authentication and fields
    Convex Lake
    Dataset3.5Editorial

    Retrieve historical prediction and options datasets for depth research, model testing and repeatable batch ingestion.

    • Access API · MCP

    Also in Historical Data and Archives.

    PolySocket official wallet-feed presentation with provider JSON example
    PolySocket
    Data feed3.5Editorial

    An authenticated live wallet-activity feed that leaves sizing, risk checks, signing and order routing to your application.

    • Access WebSocket API

    Combine historical market records with a separate live wallet-activity feed.

    Frequently asked questions about OutcomeTick

    Does a monthly plan unlock all history?

    No. It covers a rolling 30-day window; older archive data is purchased separately.

    Why are event and receive times separate?

    Event time records when an event occurred; receive time records when the collector observed it. A replay needs that distinction to avoid assuming earlier knowledge.

    What are the listed costs?

    A rolling 30-day archive costs $10/month for one venue or $18/month for both. Older history is separate, and hosted backtests start at $2 with work-scanned usage billing.

    Can I inspect data before paying?

    Yes, public samples are available. Downloading paid archive files requires an API key.