> For the complete documentation index, see [llms.txt](https://vigil-1.gitbook.io/vigil-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://vigil-1.gitbook.io/vigil-docs/sentinel-program/sentinel-handbook.md).

# Sentinel Handbook

What's expected month to month, what you earn, and how to talk about Vigil.

## Monthly goal

Each month, meet **one** of these:

* Bring in 5 or more active trading users, or
* Be an active trading user yourself

{% hint style="info" %}
**Active trading user** = a wallet that has funded at least $100, still holds $100+ after 14 days, and has real trading volume within 30 days.
{% endhint %}

Content and events are encouraged. There's no minimum count for either.

## Day to day

| What              | How                                                                                      |
| ----------------- | ---------------------------------------------------------------------------------------- |
| **Self-report**   | Every two weeks, a short form with your content links and event info. Under two minutes. |
| **Spot checks**   | We review a sample of submitted content.                                                 |
| **User activity** | Tracked automatically. You don't report it.                                              |

If you miss the monthly goal, we'll check in first to see what's in the way. If it's missed two months in a row, Sentinel perks are paused and the badge is removed.

## What you get

* **Referral earnings** — a share of fees from users you bring in, at a higher Sentinel rate
* **Rewards for market insight** — good calls and research are recognized
* **Bonuses** for standout months
* **Priority access** to new features and the product team

## Talking about Vigil

You're representing Vigil in public. A few rules matter.

**Please do:**

* ✅ Share your real experience and real trade records
* ✅ Show what the product does and how it works
* ✅ Disclose the partnership — always tag Vigil's handle

**Please don't:**

* ❌ Promise returns or suggest guaranteed results
* ❌ Make trading decisions for other people
* ❌ Overstate what the agent can do
* ❌ Post low-effort, AI-generated filler

People trade real money with Vigil. Overselling it doesn't just hurt the brand, it puts your audience at risk. When in doubt, say less and show more.

## Questions

Ask in the Sentinel channel or on X. See [Community & Links](/vigil-docs/community-and-links/community-and-links.md).


---

# 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://vigil-1.gitbook.io/vigil-docs/sentinel-program/sentinel-handbook.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.