> 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/protocol/builders-program.md).

# Builder's Program

Partner exchanges, aggregators, and alternative frontends can tap into VDEX's liquidity and technology through the Builder's program. This allows a protocol to soft fork VDEXCore for their own user base. If accepted, partners have the ability to:

* Charge and collect 100% of their own fees
* Add and remove features
  * Such as a social platform exchanging the darkpool for transparent leaderboards
* Input and discretion on pair listings

Trades on VDEX via partners continue to settle peer-to-peer on the same VDEXCore network. Soft forks and new users strengthen the decentralization of VDEX as an underlying technology layer. To apply or learn more, reach out to <hello@vdex.trade>.


---

# 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.vdex.trade/protocol/builders-program.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.
