> For the complete documentation index, see [llms.txt](https://docs.riskprotocol.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.riskprotocol.io/resources/points-program.md).

# Points Program

Real Usage. Real Rewards.

The Points Program is how The Risk Protocol rewards the people who make it work and grow—traders, liquidity providers, referrers, and community contributors who choose to build the protocol alongside us.

Most crypto points programs reward mercenary farming and vanity metrics. RISK Points reward genuine contribution. They accrue across four categories: real protocol usage, referrals that bring in actual users, skill in our monthly Trading Competition, and discretionary recognition for education, feedback, and community building.

The three pages below cover the program in detail:

**Points Principles**—the design philosophy and how points are earned across all four categories.

{% content-ref url="/pages/xkBMJYPsGp6T0S7BoN8E" %}
[Points Principles](/resources/points-program/points-principles.md)
{% endcontent-ref %}

**Referral Rewards**—rebates for bringing in users who actually trade. People you refer get rewarded too.

{% content-ref url="/pages/00m6gh0Yf5a6N9gxr2JT" %}
[Referral Rewards](/resources/points-program/referral-rewards.md)
{% endcontent-ref %}

**Trading Competition**—monthly rounds, scoring methodology, and the path to the Risk Championship.

{% content-ref url="/pages/KbhnwaM5H7Z3DCrCE3tI" %}
[Trading Competition](/resources/points-program/trading-competition.md)
{% endcontent-ref %}


---

# 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.riskprotocol.io/resources/points-program.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.