> 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/seer-solution/prediction-market-actors.md).

# Prediction Market Actors

We can see prediction markets as three-sided marketplaces comprising of:

* **Traders** (market takers): Take positions in the outcome of some event. Their motivations can vary and includes:
  * Making money by making correct predictions (most common).
  * Showing support for a particular “team” (common in political and sport markets).
  * Having fun while following some event as they have a stake in it.
  * Edging a particular risk (such as taking positions on catastrophes which would affect them).
* **Liquidity providers** (market makers): Make some orders to be taken by traders. Want to earn some return on the capital they deploy. Their risk profile may vary, but they generally prefer to stay as neutral as possible in markets and take as few risks as possible. They are interested to participate if their expected risk-adjusted yield (the APR they get discounted by how risky providing liquidity is) is higher than alternatives.
* **Information seekers**: We introduce this group of actors which were often overlooked by other prediction market initiatives. Information seekers want to either:
  * Pay in order to get some information about the likelihood of some event.\
    For example an insurance company may wish to assess the risk of an earthquake in a particular area, in order to decide the pricing of their policies. They are OK paying some money to do so, as they should make that up by having a better pricing of their insurance products.
  * Pay in order to convince others of the likelihood of some event.\
    Taking back the state actor example, the US could have benefited from paying in order to convince other nations that Russia would attack Ukraine.


---

# 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/seer-solution/prediction-market-actors.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.