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

# Market Creation

## Any user can create a new prediction market by specifying a question and parameters for the event. The key parameter is a **token address** – this links the market to a particular pump.fun token and allows the platform to fetch relevant data (price, market cap, holder counts, etc.) for evaluating the outcome. For example, a market could be *“Will Token X reach a market cap of 1,000 SOL by Oct 31, 2025?”* with Token X’s address provided to track its market capitalization. When creating a market, the creator defines the outcomes (typically **Yes** or **No**) and an expiration time or block height when the market will resolve. An initial stake (in SOL or $POLYPUMP) may be required from the creator to seed the market’s liquidity and signal confidence in the event.

<figure><img src="/files/GECQOO0etlsEfXjg9wgY" alt=""><figcaption></figcaption></figure>


---

# 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://docs.polypump.app/documentation/how-it-works/quickstart.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.
