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

# Points & Rewards

Every action earns points that build your rank and unlock perks.

| Action                 | Reward                    |
| ---------------------- | ------------------------- |
| 1 SOL wagered          | 200 points                |
| Winning a round        | +300 points               |
| Referred player wagers | +25 points per SOL        |
| Daily login            | +50 points (once per day) |

So if you log in, bet 2 SOL, and win once, that’s:

* 2 SOL × 200 pts = **400 pts**
* Win bonus = **+300 pts**
* Daily bonus = **+50 pts**\
  ➡️ **750 pts in one session**

That already puts you close to **Silver**.

Points update in real time on the **Rewards Dashboard**.


---

# 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://house-games.gitbook.io/house-games-docs/points-and-rewards.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.