> For the complete documentation index, see [llms.txt](https://docs.prebit.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.prebit.io/readme/mission-and-vision.md).

# Mission and Vision

### **Mission**<br>

At Prebit, we aim to redefine decentralized trading by expanding features such as binary options, price predictions, and advanced order types, all while maintaining the lowest fees and tightest spreads. As one of the top gas spenders on BNB Smart Chain, our focus is on simplicity, speed, and efficiency in smart contract execution to deliver the fastest and most user-friendly decentralized trading experience.

### **Vision**<br>

Our vision is to establish Prebit as a leader in the decentralized exchange industry within the next year. We aspire to become the most transparent and efficient perpetual DEX, known for ease of registration, unparalleled speed, and robust trading features. With a unicorn perspective, Prebit is set to define the future of decentralized trading.

<br>


---

# 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://docs.prebit.io/readme/mission-and-vision.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.
