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

# User Experience

Despite its technical sophistication, Seerdex is designed to be intuitive and accessible. Users interact with the platform through a streamlined interface that abstracts away much of the underlying complexity.

{% stepper %}
{% step %}

## Connect a wallet.

{% endstep %}

{% step %}

## Deposit SEERX or Stablecoins

{% endstep %}

{% step %}

## Select a market of interest

Take a position by purchasing YES or NO shares, with prices reflecting real-time probabilities derived from market activity.
{% endstep %}
{% endstepper %}

For example, if a market assigns a **35% probability** to Bitcoin reaching a certain price level, YES shares will trade at approximately **$0.35**. If the event occurs, those shares settle at **$1.00**, creating a clear and transparent payoff structure. If it does not, they settle at $0. This pricing makes the cost, the potential reward, and the implied odds easy to understand at a glance — no complex formulas required.


---

# 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://seerdex.gitbook.io/seerdex-whitepaper/user-experience.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.