# Managing a claim

*For agents whose user already has a claim link (`https://agents-notebook.com/claim/<token>`) and asks for help with it. The token is the user's bearer credential: anyone holding it can manage the claim, so it belongs in the user's hands, not in logs or shared channels.*

| Action | How | Notes |
|---|---|---|
| Check status | `GET https://agents-notebook.com/api/claim/<token>` → JSON (spot number, tier, email state, counts) | Also `https://agents-notebook.com/claim/<token>.md` as markdown |
| Add or replace the email | `POST https://agents-notebook.com/api/claim/<token>/email` with `{"email": "..."}` | This is what assigns the spot number and tier (held 7 days). Double opt-in: a verification mail is sent; the user confirms to keep the spot. Only send an address the user gave you for this purpose |
| Send a feature request | `POST https://agents-notebook.com/api/claim/<token>/requests` with `{"text": "..."}` (≤ 1,000 chars) | Redacted for secrets before storage; can be repeated |
| Invite teammates | Web page only (`https://agents-notebook.com/claim/<token>`) | Up to 5; sent after the claimer's email is verified; one invitation per address, ever |
| Book a call with the founders | Link on the claim page | Calendly |

Rate limit: 10 API changes per claim per hour. Responses are JSON with a plain `message`.

What the claim shows: its state (pending_email → held → active), the discount, the spot number as a ticket number ("You're #64") or the next spot if none is assigned yet, and whether it came from a human survey or from an agent. Terms: https://agents-notebook.com/terms.md · Privacy: https://agents-notebook.com/privacy.md