> For the complete documentation index, see [llms.txt](https://doc.d1ce.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.d1ce.com/blog-en/what-is-weekly-bonus.md).

# What is Weekly Bonus?

### **Who is eligible for the Weekly Bonus?**

All VIP players from Bronze level upwards are eligible.

### **When is the Weekly Bonus sent out?**

Every Saturday at 00:00 (GMT+8).

### **Where is the Weekly Bonus posted and how do I claim it?**

Please navigate to the VIP page and select "Weekly Bonus" to claim your exclusive benefits.

### **How is the Weekly Bonus calculated?**

Here are some of the details that are taken into account when calculating the weekly bonus:&#x20;

* Your VIP rank.
* Your wagered amount in the last 7 days.&#x20;

### **When does the Weekly Bonus link expire?**

From the moment they're posted, weekly bonus links last for 4 weeks.


---

# 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://doc.d1ce.com/blog-en/what-is-weekly-bonus.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.
