> For the complete documentation index, see [llms.txt](https://trex-1.gitbook.io/trex/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://trex-1.gitbook.io/trex/open-ecosystem-and-culture/ecosystem-points.md).
# Ecosystem Points
Recognition in T-Rex is not limited to Badges alone. To capture the rhythm of ongoing activity, the systme introduces **Ecosystem Points**, a measure of engagement that flows across the Passport.
Each Badge minted has an associated point value. A governance streak, a liquidity milestone, or a developer credential all translate into points that reflect contribution. Social actions can also be rewarded, from participating in events to verified community engagement. Over time, these points accumulate into a visible signal of how deeply a person participates in the ecosystem.
Unlike tokens that are bound to speculation, Ecosystem Points are bound to activity. They are earned through real behavior and can't be bought. Because they live inside the T-Rex Passport, they are portable across applications. A DAO can use them to gate access, a game can use them to reward loyal players, and a platform can use them to identify trusted users.
Points also create a secondary layer of recognition. Where Badges highlight specific achievements, Ecosystem Points give a broader sense of momentum: how active someone has been, how consistent, how engaged. They are a flexible metric that complements verifiable credentials with a running measure of contribution.
Ecosystem Points makes engagement legible. They ensure that effort is never lost, but carried across contexts as part of the Value Graph. In doing so, they reinforce the principle that in T-Rex, participation is valuable.
---
# 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://trex-1.gitbook.io/trex/open-ecosystem-and-culture/ecosystem-points.md?ask=&goal=
```
`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.