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

# About trade\[XYZ]

trade\[XYZ] and our products on Hyperliquid.

We believe global capital markets should be broadly accessible, with deep liquidity available 24/7. Our mission is empower you ***to trade anything, anytime.***

To achieve this goal, we deploy novel financial primitives and trading experiences on Hyperliquid that extend the range of assets and events that can be traded on HyperCore while preserving the benefits of Hyperliquid's leading onchain infrastructure. 

This documentation covers two products:

* [**Perpetuals**](/perpetuals.md). Perpetual markets deployed through [HIP-3](https://hyperliquid.gitbook.io/hyperliquid-docs/hyperliquid-improvement-proposals-hips/hip-3-builder-deployed-perpetuals), including stocks, equity indices, commodities, currencies, and pre-IPO markets.
* [**Events**](/events.md). Fully collateralized event contracts deployed through [HIP-4](https://hyperliquid.gitbook.io/hyperliquid-docs/hyperliquid-improvement-proposals-hips/hip-4-outcome-markets), with fixed settlement rules and no leverage or liquidations.

trade\[XYZ] also provides a non-custodial interface for interacting with these and other Hyperliquid markets. The interface does not hold user assets or operate HyperCore, and it is not the exclusive way to access trade\[XYZ] markets.

Use these docs to understand the products’ architecture, mechanics, specifications, risks, and for other resources. Before accessing these products, please also review the [Legal and Disclaimers](/legal-and-disclaimers/general-disclaimer.md) section as well as any applicable market specifications.


---

# 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.trade.xyz/overview/about-trade-xyz.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.