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

# About

#### What is VDEX?

VDEX is the global capital marketplace where you can trade anything, anywhere. For the first time, users can buy crypto, stocks, commodities, FX, and prediction markets all on the same platform.

#### Mission

Self-custody and privacy are inalienable human rights. These rights must be upheld without imposing costs or compromising experience. VDEX fulfills this vision by unifying the control of a DEX with the performance of a CEX:

<p align="center"><strong>An immutable dark pool with sub-millisecond finality and Zero Fees.</strong></p>

#### Core Contributors

[Virtual Labs](https://virtuallabs.xyz/) is a core contributor supporting the growth of VDEX.


---

# 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 following URL with the `ask` and `goal` query parameters:

```
GET https://docs.vdex.trade/introduction/quickstart.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 `build a script that syncs our docs to a CMS` 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.
