Use a Limitless market link and time range to review saved historical prices for its “Yes” outcome.
Up to 0.01122 credits / call
The final charge is based on confirmed usage. Unused reserved credits return to your available balance.
BlockRun
Limitless Order Book History | BlockRun
Use a Limitless market link and time range to review saved historical prices for its “Yes” outcome.
You receive
Recorded YES-side order-book snapshots for your market and interval when available, with bid/ask price levels and sizes, timestamps and reported midpoint values. Your Agent can compare these across the returned observations.
Start with your task
For [Limitless market link], show up to five saved historical price records between [start date and time, including time zone] and [end date and time, including time zone]. Focus on the “Yes” outcome, compare the recorded buy and sell prices, and tell me if no records are available.
What to know
A response may be empty or incomplete. Level-size units and midpoint calculation methods are not documented, so the records do not establish traded value or guaranteed execution. The native response covers the YES side; a NO view is an additional derived presentation.
Inputs & outputs
Inspect the current inputs, availability, and maximum charge before starting.
Input schema
Input schema
Field / Path
Type
Requirement
Meaning
Market and time rangequeryParams
object
Optional
Put market_slug plus both start_time and end_time directly here. The time boundaries must be integer Unix milliseconds. Optional limit and pagination_key also belong in this container.
Nested query objectqueryParams.query
object
Optional
This optional nested object does not flatten into the order-book request. Put the required market/time values and optional page controls directly in queryParams.
Opaque cursor when available. Preserve the exact returned string; null is not a usable next-page key.
Additional notes
Specify a market and interval
Provide the Limitless market slug and both the start and end of the period you want to inspect. start_time and end_time must be integer Unix milliseconds. When using calendar times, include the time zone so the Agent can convert both boundaries correctly. The supplier does not define default boundaries, a maximum interval or whether each boundary is inclusive.
Put market_slug, start_time and end_time directly in queryParams. queryParams.query does not flatten into the request. The only additional query controls are limit, an integer from 1 to 200 with a default of 100, and pagination_key for continuation. There is no side selector, token-ID filter or custom snapshot interval.
Read the YES-side order book
When observations are available, the supplier describes each snapshot with a market slug, YES token metadata, a millisecond timestamp, bids for buying YES and asks for selling YES. Each level has a price and size. Level prices are described as 0–1; the size unit is not specified. Do not infer traded volume, dollar value or a guaranteed executable quote from these values.
midpoint and adjusted_midpoint are separate returned price values. The source does not define either calculation or the adjustment method, so keep them as supplied rather than replacing them with a calculated average. The native response contains only the YES-side book. If you need a NO view, the source describes a client-side transformation that swaps bids and asks and uses 1 minus each price. An Agent can show that derived view separately while retaining the original YES data; it is not an independently observed NO book.
Account for gaps and pages
The supplier states that data starts on March 7, 2026. It does not guarantee every market's availability, complete depth, a fixed recording cadence or the ordering of levels and snapshots. An empty response cannot establish that no order book existed during the interval. count is the number of snapshots on the current page; has_more indicates additional records and pagination_key is an opaque cursor when supplied.
See the Predexon Limitless order-book documentation for the exact supplier definitions. Follow the Toolmu connection guide to connect your Agent. Your Agent can compare returned bid/ask levels and reported midpoint values across available observations; this data query does not place an order.
Use your connected AI assistant
Copy the request above into the assistant you connected to Toolmu. If you have not connected one yet, follow the connection guide.
Open the Limitless market page you want to check and copy its link. Add a start and end date/time with the time zone. If the market repeats, use the link for the exact past round. You do not need to find a separate code or convert the time yourself.
For [Limitless market link], show up to five saved historical price records between [start date and time, including time zone] and [end date and time, including time zone]. Focus on the “Yes” outcome, compare the recorded buy and sell prices, and tell me if no records are available.
Review the saved prices
The records cover only the market’s “Yes” outcome. The service may have fewer than five records or none. No result does not prove that the market had no price at that time.
