> 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-zh-tw/sheng-ri-jiang-li-shi-shen-mo.md).

# 生日獎勵是什麼？

### 我如何符合資格？

必須符合以下條件：

* 擁有已驗證的電子郵件地址。
* 在生日當天前完成至少 2 級 KYC 驗證。
* 保持帳戶活躍度或達到 VIP 等級（金級-黑曜石級）。

### 我將如何收到獎勵？

如果您符合資格條件，請在您的生日當天留意您的收件匣。D1CE 將會發送一封包含有效期為 7 天的優惠券連結的電子郵件。&#x20;

\ <br>


---

# 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-zh-tw/sheng-ri-jiang-li-shi-shen-mo.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.
