> For the complete documentation index, see [llms.txt](https://docs.dreamos.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dreamos.app/fees.md).

# Fees

Dream charges a 2% fee on the premium paid to open an options position.

There is no additional fee charged by Dream when closing a position.

### Opening Fee

The opening fee is calculated as:

Opening Fee = Option Premium × 2%

For example:

| <p><br></p>       | Amount |
| ----------------- | ------ |
| Total amount paid | $100   |
| Opening fee (2%)  | $2     |
| Premium           | $98    |

The opening fee is included in your displayed cost basis and is reflected in your position's profit and loss calculations.

### Closing Fee

Dream does not charge a separate closing fee.

However, the price available when closing a position may differ from the price paid to open it because of the bid-ask spread and changes in the option's market value.

### Fees vs. Spreads

Dream's opening fee and the bid-ask spread are separate.

The opening fee is charged by Dream.

The spread reflects the difference between the buying and selling prices provided by liquidity providers.

For more information, see Pricing and Spreads.


---

# 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.dreamos.app/fees.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.