> For the complete documentation index, see [llms.txt](https://docs.opinion.trade/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.opinion.trade/trade-on-opinion.trade/trade-on-prediction-market/start-trading.md).
# Start trading
## Choosing Market
On [opinion.trade](https://app.opinion.trade/), finding a market is easy. Head to the market page to view all available markets. From there, you can refine your search using filters, sorting options, and search tools to target the events you're most interested in.
## Buying Shares
After selecting the market you want to trade, click on it to see all the relevant details.\
On the market page, you’ll find a graph, market rules, and current odds to guide your decision.\
To make your trade, follow these steps using the ‘Buy’ panel on the right:
1. Choose the outcome you wish to buy (generally Yes or No).
2. Enter your desired dollar amount.
3. Click Buy to confirm.
After your trade goes through, you'll receive a confirmation notification. Congratulations—you’ve made your first trade on opinion.trade!
Keep in mind, you’re free to sell your position at any point before the market closes, using the current odds.
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.opinion.trade/trade-on-opinion.trade/trade-on-prediction-market/start-trading.md?ask=&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 `automate deployments from our CI pipeline` 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.
