> 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/about-trade-xyz/introduction.md).

# Introduction

This documentation is intended to provide you with support and resources to get started using trade\[XYZ]. If you have questions that aren’t answered here or other technical issues, please reach out to support via our help channels in the interface or app.

trade\[xyz] is a non-custodial interface built to enable a simple and powerful trading experience. The interface allows users to interact with markets on HyperCore, a performant decentralized orderbook exchange on the Hyperliquid blockchain. These markets include HIP-3 deployed perpetual markets.

While we hope to one day enable access to markets globally, current legal requirements means our interface may be unavailable in certain restricted jurisdictions. This includes the U.S. and other restricted jurisdictions that may be subject to comprehensive sanctions or where we otherwise determine to restrict access. We also may screen wallets for sanctions risk. You can read more about eligibility to use the interface in our terms.


---

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