> For the complete documentation index, see [llms.txt](https://docs.stratium.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.stratium.xyz/about-stratium/introduction.md).
# Introduction
Stratium is a structured-finance protocol built on Hyperliquid.
Two products are running today.
**Perpetuals.** Live on Hyperliquid at [trade.stratium.xyz](https://trade.stratium.xyz), through Stratium's Builder Code. Every perpetual listed on Hyperliquid is tradable through the terminal. Planning for a deployment through HIP-3.
**Binary options.** Running on [markets.stratium.xyz](https://markets.stratium.xyz), ahead of mainnet deployment through HIP-4.
A third product, srHYPE liquid staking, has contracts deployed on HyperEVM at [app.stratium.xyz](https://app.stratium.xyz).
#### What we are building toward
Structured products are a multi-trillion-dollar category in traditional finance. They are the instruments institutions use to construct risk, manufacture yield, and convert uncertainty into a defined payoff. For fifty years they lived on bank balance sheets. They were priced in back offices, settled over days, and reached only through private relationships.
The instrument design was never the barrier. The opacity was.
Onchain infrastructure removes that barrier. Payoff logic is public. Settlement is composable. There is no issuing counterparty, no issuance cycle, and no minimum ticket size.
Stratium is building that layer on Hyperliquid, starting with the two products above and expanding into markets that require purpose-built price feeds.
---
# 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.stratium.xyz/about-stratium/introduction.md?ask=&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.
