# Introduction ### About Cube is a hybrid exchange built from first principles for the future of digital and traditional asset trading. At it's core, a low-latency matching engine powers trading at 200'000 operations per second with 200µs latency, and a decentralized settlement layer powers a non-custodial peer-to-peer settlement that ensures the safety of your assets. ### Overview This documentation covers a large part of the Cube API, and is roughly organized into the following: * [Exchange Info](/cube-api/exchange-info.md): Information about the exchange, such as assets, markets, account management, and more. * [Market Data](/cube-api/market-data/rest-api.md): Market data, including level 3 (order by order) book data, trade summaries, and more. * [Order Entry](/cube-api/order-entry/rest-api.md): Trading and order management. * [Perpetual Futures](/cube-api/perpetual-futures.md): Information about our perpetual futures contracts, including contract specifications, margin requirements, funding, settlement, and liquidation. * [Fees](/cube-api/fees/cube-fees.md): Information about fees on Cube. #### Connectivity * **REST**: For market data snapshots and order entry. * **Websocket**: For realtime market data and trading. * **TCP FIX and UDP Multicast**: Out lowest latency connectivity. Reach out for more information. ### Environments If you're interested in building with us, reach out about getting access to our staging environment, where you can test your integrations before going live! ### Contact Reach out to us at for questions or feedback! --- # Agent Instructions: 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: ``` GET https://cubexch.gitbook.io/cube-api/readme.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.