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

# Referral Program

The Bounce referral program rewards both referrers and referred users. To check your referral status and claim rewards, go to the referrals page:

<https://bounce.tech/referrals>

#### How do I generate a referral code?&#x20;

Users become eligible to create a referral code after reaching $100,000 in total notional trading volume on Bounce. Check your eligibility [here](https://bounce.tech/referrals).

#### What will I earn for referring users?&#x20;

You will earn 10% of the redemption fees generated by users who trade through your referral code.&#x20;

#### How do I use a referral code?&#x20;

You can use a referral code by connecting to Bounce via a referral link. Once a referral code is applied, you will receive a 4% rebate on redemption fees.&#x20;

#### How do I become an affiliate?

The Bounce affiliate program is invite-only and is currently available to:

* Users with $1,000,000+ in total trading volume
* Approved partners and community members

Affiliates may receive enhanced referral benefits and additional partnership opportunities.&#x20;

To apply for the affiliate program, contact @maxbphi on [Telegram](https://t.me/maxbphi).


---

# 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.bounce.tech/community/referral-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.