> For the complete documentation index, see [llms.txt](https://docs.42.space/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.42.space/getting-started/publish-your-docs/trading-eventcoins/buying-an-outcome.md).

# Buying an outcome

{% stepper %}
{% step %}

### Select outcome

Select the outcome you want to back
{% endstep %}

{% step %}

### Enter amount in USDT

Live preview of how your expected payout changes after you enter the position. Payouts are not fixed—they update as other participants buy or sell the same outcome.

{% hint style="info" %}
Learn more in [Payout Mechanics](/getting-started/protocol-mechanics-101/convex-payout-dynamics.md#payout-mechanics).
{% endhint %}
{% endstep %}

{% step %}

### Buy

Confirm your order
{% endstep %}

{% step %}

### Share Outcome Card (Optional)

Flex your position and the potential winnings of what you just bought
{% endstep %}
{% endstepper %}

After buying an outcome, you can choose to 

* Take profit by [Selling an outcome](/getting-started/publish-your-docs/trading-eventcoins/selling-an-outcome.md) if you observe more participants buying the same outcome (your payout may improve as flow shifts).
* Hold until resolution. If your outcome wins, your tokens share the resolved market’s Total Market Cap with other winning holders. If it loses, the token’s value goes to $0.


---

# 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.42.space/getting-started/publish-your-docs/trading-eventcoins/buying-an-outcome.md?ask=<question>&goal=<user_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.