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

# What is Dream?

Dream is a mobile-first options brokerage that provides access to institutional-grade liquidity through a simple, intuitive trading interface.

Dream aggregates quotes from institutional liquidity providers, allowing users to trade options across a wide range of digital assets, with expiries ranging from the same day to one year out.

Rather than navigating traditional options order books, users can select an asset, choose a strike price and expiration date, and receive pricing for their trade.

Dream combines onchain wallet functionality with an options brokerage designed to make opening, managing, and closing positions straightforward. Options on Dream are cash-settled. Users can receive a cash payout at expiration rather than taking delivery of the underlying asset.

Whether trading short-term price movements or expressing a longer-term view on an asset, users can access options across supported markets and contract sizes.


---

# 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.dream.trade/introduction/what-is-dream.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.
