> 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/incentives/indexify-points.md).

# Indexify Points

#### **How it works**

* **1 Point = $1 in trading volume**
* You earn **Points for every dollar traded personally**
* You earn **Points for every dollar traded on your Stacks that you created**
* **Stack creation** also earns Points
* Both **buy and sell** volume count
* Points accumulate as you stay active

#### **Why it matters**

* Points reflect your overall platform activity
* They build your reputation as both a trader and a creator
* Points unlock future perks, benefits, and reward opportunities

#### **Boosts & Bonuses**

Keep an eye out for **Points Boosts -** special, time-limited multipliers that increase how many Points you earn from trading volume or Stack activity.\
Boost windows are the best way to maximize your Points and reward growth, and will be announced on our X or Discord page.

***

> 📊 **Tracking**\
> Your Points balance and reward history can be viewed in your **Incentives or Portfolio page**.


---

# 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/incentives/indexify-points.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.