> For the complete documentation index, see [llms.txt](https://docs.lumefi.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.lumefi.app/getting-started/refer-and-earn-40.md).

# Refer & Earn 40%

Lume referral system

We’re excited to introduce **Lume’s Referral Program**, designed to reward you for helping grow our trading community. **Earn passive income every time your referrals trade on Lume** — **more trading volume = higher earnings.** 📈Invite friends, get paid.  Lume offers a **stunning 40% referral reward** to users.

#### **How it works**

* **Get your unique referral link** and Share it anywhere ( X, WhatsApp, Telegram, Discord etc.)&#x20;
* When a user joins via your link and transacts, you earn **40% of Lume’s referral commission** from their **eligible fees** (e.g., trading fees, prediction fees)
* **Claim** your rewards from rewards dashboard.
* **Thresholds & expiry:** Minimum claim thresholds and expiries (if any) are displayed in-app.

#### **Example**

* Your refer John who Trade  $10,000 in a day
* **Lume’s eligible fees:** $10,000 × **1%** = **$100**
* Your reward = **40% × $100 = $40**
* **Plus bonus:** You also earn **Lume Points**


---

# 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 following URL with the `ask` and `goal` query parameters:

```
GET https://docs.lumefi.app/getting-started/refer-and-earn-40.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 `build a script that syncs our docs to a CMS` 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.
