> For the complete documentation index, see [llms.txt](https://docs.helixapp.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.helixapp.com/trading/perpetuals/tradfi-stocks-index-tradfi.md).

# TradFi Stocks Index (TRADFI)

**Overview**

The TradFi Stocks Index is an index designed to provide investors with diversified exposure to hundreds of the largest publicly-traded equities in the US.&#x20;

#### **Index Value**

The index is priced by formulaically aggregating the nominal prices of each equity component's market cap. The mark price is provided for this [product by Pyth](https://www.pyth.network/price-feeds/equity-us-spy-usd).

**Trading**

Like all other perpetual futures contracts on Helix, the TradFi Stocks Index is a derivative product with leverage. This specific product has a maximum leverage of 25x, with an initial margin of 3.33% and maintenance margin of 2%. The pair trades 24/7/365, though the oracle only updates during typical NYSE trading hours, from 2:30pm UTC to 9pm UTC on weekdays (except NYSE trading holidays).


---

# 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.helixapp.com/trading/perpetuals/tradfi-stocks-index-tradfi.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.
