> For the complete documentation index, see [llms.txt](https://velocity-1.gitbook.io/velocity-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://velocity-1.gitbook.io/velocity-docs/about/team.md). # Team Velocity is built by a team from across crypto and traditional finance, with backgrounds in venture capital, exchanges, and banking. Members have worked with some of the largest exchanges, market makers, and companies in crypto, including OKX, Crypto.com, Bybit, and Blofin, among many more. That mix shapes how we build. We have run trading and operations at scale on centralised venues, and we have built and invested across DeFi. From both sides we kept hitting the same flaws: centralised exchanges make you give up custody and trust a black box, while DeFi, for all its openness, still falls short on execution, market design, and user experience. We started Velocity to fix that. We are building a trading product for professional traders and businesses that pairs the depth, speed, and reliability of a top centralised exchange with the custody and transparency of on-chain markets, all in a premium, professional-grade interface across multiple venues. That is the bar we hold every part of Velocity to. --- # 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://velocity-1.gitbook.io/velocity-docs/about/team.md?ask=&goal= ``` `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.