> For the complete documentation index, see [llms.txt](https://stablemesh.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://stablemesh.gitbook.io/docs/home/stablemesh-doc/invite-earn.md).

# Invite & Earn

Share Stable Mesh with friends and earn rewards every time someone signs up and starts using the platform through your referral link.

***

## How It Works

1. Click **Invite & Earn** in the top navigation bar.
2. Copy your unique referral link.
3. Share it with friends, colleagues, or your community.
4. When they sign up and use Stable Mesh, **you both earn rewards**.

***

## Tips for Sharing

* Share in crypto communities and Telegram groups
* Include your link in blog posts or social media
* Refer your team if you use Stable Mesh for business expenses

***

{% hint style="info" %}
Reward terms and rates are shown in the Invite & Earn section of the app. Check there for the latest details on how rewards are calculated and paid out.
{% 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 dynamically by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://stablemesh.gitbook.io/docs/home/stablemesh-doc/invite-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 `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.