> For the complete documentation index, see [llms.txt](https://docs.timeless.market/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.timeless.market/getting-started/quickstart.md).

# What is Timeless Market?

Timeless Market enables anyone to trade on the outcome of real-world and on-chain events through simple “Yes” or “No” shares - creating an open, decentralized prediction and risk market. Users can buy shares representing the probability of an outcome.

> For example, purchasing a “Yes” share in “BTC will reach $100k by 2025” at $0.25 implies a 25% market-assessed chance that the event will happen. If the prediction resolves true, each “Yes” share settles at $1, while losing shares expire worthless - offering a potential return of up to 4x in this case.

Each market is collateralized through on-chain smart contracts. Before resolution, 1 “Yes” + 1 “No” share in a given market can always be redeemed together for 1 collateral token, ensuring the system remains fully backed and risk-balanced. Collateral tokens - typically USD1 - are locked within the protocol to provide transparent settlement and instant liquidity for all participants.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.timeless.market/getting-started/quickstart.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `build a script that syncs our docs to a CMS` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
