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

# Refer & Earn

Guides, setup instructions, and tips for individual Permission Agent users

The Permission Referral Program is an easy way to boost your ASK balance while introducing others to the benefits of Permission.

Invite friends to join the Permission ecosystem and you’ll both earn bonus rewards. 

### How It Works

1. **Get Your Referral Link**
   * Sign in to your Permission account.
   * Go to **Referral Program** in your dashboard to find your unique link.
2. **Invite Friends**
   * Share your link by email, social media, or direct message.
3. **Earn Rewards**
   * When someone signs up using your link and activates a Permission account, you both earn a **bonus ASK reward**.

### Reward Structure

* **You earn**:
  * A one-time ASK bonus when your referral activates the Permission Agent.
* **They earn**:
  * A one-time ASK bonus for joining via your link.

Rewards drop straight into your Permission Wallet like magic.

### Track Your Progress

You can track your referrals any time from the **Referral Program** section of your Permission dashboard.


---

# 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.permission.ai/refer-and-earn.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.