> For the complete documentation index, see [llms.txt](https://seer-2.gitbook.io/seer/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://seer-2.gitbook.io/seer/applications.md).

# Applications

We expect Seer prediction markets to be initially visible in one general purpose frontend. In order to prevent spam and « tricky » (markets likely to be invalid or markets whose literal interpretation is very different from what most people initially understand) markets, we’ll use Kleros Curate \[28] similarly to Omen \[29].

As the project advances, we could have more specialised frontends, each dealing with a special usecase. Those could even have their own governance.

Note that you may not be convinced or support all those applications. But the idea is for Seer to be a neutral protocol (it should still have some limits and abhorrent markets such as assassination markets shouldn’t be listed by frontends nor supported by Kleros) and different contributors would contribute to different usecases.

<br>


---

# 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://seer-2.gitbook.io/seer/applications.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.