> For the complete documentation index, see [llms.txt](https://docs.allocations.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.allocations.com/openstocks-manual-v2/08-how-it-works.md).

# 08 How it works

How it Works is the OpenStocks FAQ. Read it before your first trade.

![](https://content.gitbook.com/content/9IirLidzibYpEfSBave3/blobs/UeILGter0dcRQ5LUjrtj/Unknown%20image)

1. **Subject heading**\
   Groups related questions under one subject.
2. **Question**\
   Shows the answer when you select it.
3. **Expand control**\
   Opens or closes the answer.

## Getting started

This section answers five questions: what is listed, how to place a trade, which exchanges you can use, what you need first, and where your tokens appear afterward. The same steps are described in **Placing a trade**.

## Pricing and market data

This section answers four questions: how the token price is set, what the trade desk figures mean, how the final price is set on the exchange, and how to verify a token on BscScan. Read the answer on the final price before your first trade.

## Security and integration

This section answers three questions: who holds your tokens, how positions are protected, and what a pre-IPO token gives you.


---

# 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.allocations.com/openstocks-manual-v2/08-how-it-works.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.
