> For the complete documentation index, see [llms.txt](https://pendle.gitbook.io/boros/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://pendle.gitbook.io/boros/boros-docs/others/boros-referral-program.md).
# Boros Referral Program
You can access the referral page at Boros' account page:
* Using a referral code will give you a 10% discount on swap fees.
* Referrers will receive 20% of all fees generated by the code.
## Eligibility
We encourage fresh addresses to use referral codes! Addresses with trading volume exceeding $100,000 notional value will no longer be eligible to use a referral code.
To generate a referral code, your address must have at least **$1,000,000 in notional trading volume**.
Upper limits for Boros referral system:
* Each address is limited to $1,000,000,000 in notional trading volume, after which the 10% discount no longer applies.
* Each referral code lasts for 1 year since it is generated.
{% hint style="warning" %}
The Boros team reserves the right to determine the eligibility of referral codes and payouts. Cases where the team deem as suspected abuse (e.g. exclusive self-referral) will result in no payout, or cancellation of codes.
{% endhint %}
---
# 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://pendle.gitbook.io/boros/boros-docs/others/boros-referral-program.md?ask=&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.
