> 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/perpetuals.md).

# Perpetuals

Perpetuals deployed by trade\[XYZ] through Hyperliquid HIP-3.

Perpetual contracts, or perps, are derivative products that provide price exposure without a fixed expiry. A funding rate mechanism helps keep a perpetual market’s price aligned with its reference price, while margin requirements, liquidations, and auto-deleveraging manage leveraged positions.

Perpetuals by trade\[XYZ] are listed on the `xyz` HIP-3 deployment. They are linear contracts margined and settled in USDC. Because the oracle is denominated in USD and no USDC/USD conversion is applied, economic exposure is *quanto*: USD profit and loss is cash-settled in USDC.

Matching, order types, funding transfers, liquidations, and auto-deleveraging are handled by HyperCore. The `xyz` deployment supplies market-specific pricing data (including the *oracle price,* the *mark price,* and the *external price* which are bespoke components*)* and parameters for assets such as stocks, equity indices, commodities, foreign exchange, and pre-IPO markets.

<table data-view="cards"><thead><tr><th></th><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td>🏗️</td><td><strong>Architecture</strong></td><td>Architecture and verified metadata for the xyz HIP-3 perpetual deployment.</td><td><a href="/architecture.md">Perpetuals Architecture</a></td></tr><tr><td>⚙️</td><td><strong>Mechanics</strong></td><td>Oracle, mark, external price, discovery bounds, and fees.</td><td><a href="/perpetuals/mechanics.md">Mechanics</a></td></tr><tr><td>📊</td><td><strong>Markets</strong></td><td>Asset classes and market-specific methodology.</td><td><a href="/perpetuals/markets.md">Markets</a></td></tr><tr><td>📋</td><td><strong>Specifications &#x26; Schedules</strong></td><td>Contract parameters, closures, and roll schedules.</td><td><a href="/perpetuals/specifications-and-schedules.md">Specifications &amp; Schedules</a></td></tr><tr><td>🛡️</td><td><strong>Risk &#x26; Margining</strong></td><td>Margin modes, liquidations, and auto-deleveraging.</td><td><a href="/perpetuals/risk-and-margining.md">Risk &amp; Margining</a></td></tr><tr><td>🕒</td><td><strong>Changelog</strong></td><td>Material updates to market mechanics and parameters.</td><td><a href="/perpetuals/changelog.md">Changelog</a></td></tr></tbody></table>


---

# 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 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/perpetuals.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 `automate deployments from our CI pipeline` 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.