> For the complete documentation index, see [llms.txt](https://howto.indexify.finance/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://howto.indexify.finance/getting-started/stacks/understanding-stack-performance.md).

# Understanding Stack Performance

Every Stack starts at **$1** when it’s created.\
The price shows how that Stack has performed since launch.

* If the Stack price is **above $1**, it’s up in value.
* If it’s **below $1**, it’s down in value.
* The percentage shown reflects the total change in value since inception.

Stack performance is based on the combined value of all assets and trades inside the Stack.\
It updates automatically as markets move and trades are made.

You can also toggle the price display by clicking your profile in the top right to view performance in **x terms** instead of dollars. For example, a **$5 Stack** is shown as **5×** in the x-view.

**Simple rule:**\
$1 is your starting point.\
Anything above means gains, anything below means losses.


---

# 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://howto.indexify.finance/getting-started/stacks/understanding-stack-performance.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.