> For the complete documentation index, see [llms.txt](https://limelight-1.gitbook.io/limelight-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://limelight-1.gitbook.io/limelight-docs/knowledge-base/recurring-markets.md).

# Recurring Markets

{% hint style="info" %}
**Coming soon.** Recurring Markets arrive in a later phase. This page previews how they'll work.
{% endhint %}

Recurring Markets are time-boxed prediction markets on observable variables — crypto prices, commodities, macro indicators — that reset on a fixed cadence. Because each instance shares an identical structure with the one before it, participants build familiarity and return with minimal friction.

## How They'll Work

* A new market instance is created automatically at each cycle for every supported asset.
* Each instance is a binary **Up or Down** market at a strike price locked at the start of the cycle (outcome 0 = UP, outcome 1 = DOWN).
* Typical cycles: 5m / 15m / 1h / 4h / 1d.

## Resolution

Recurring Markets resolve against **Pyth** price feeds read on-chain at expiry — fast, verifiable settlement with minimal manual adjudication. A short dispute window still follows each resolution. See [Market Lifecycle & Disputes](/limelight-docs/knowledge-base/market-lifecycle-and-disputes.md).

## Launch Categories *(planned)*

| Category      | Example                             |
| ------------- | ----------------------------------- |
| Crypto prices | BTC/USD above $X at the cycle close |
| Crypto prices | ETH/USD daily directional           |
| Commodities   | Gold spot price                     |
| Commodities   | WTI crude oil settlement            |
| Macro         | Rate-decision expectations          |

Additional categories will expand over time.


---

# 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 current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://limelight-1.gitbook.io/limelight-docs/knowledge-base/recurring-markets.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.