watch_mark
Start watching a mark for NEW confusingly similar filings. This CREATES a watch (a side effect — it stores the watch and sends a confirmation email with the stop link). Runs a baseline screen first — everything already on the register is marked seen, so you are only alerted on filings that appear AFTER the watch starts. Returns JSON with the watch id, its classes/threshold/schedule, and the baseline hits (for context). Check for new filings with check_watches, or let the scheduled checker run (daily by default, or weekly / every N days if you set a schedule). An email is required — it is the watch's owner, and the digest goes there (needs RESEND_API_KEY on the server; without it the watch still works and records hits, and alerts start once email is switched on). The email must be verified first — call request_watch_code, then pass the email and code (or the session token); without verification the watch is refused, so nobody can attach someone else's inbox. SCREEN ONLY — not clearance, not legal advice.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| code | No | 6-digit code from request_watch_code, for the email above | |
| name | Yes | Your mark, e.g. NOVABREW | |
| Yes | Email address for new-filing alerts (required). Must be verified — see request_watch_code. | ||
| classes | No | Nice classes (1-45) if known; otherwise inferred | |
| schedule | No | How often the scheduled checker looks at this watch: 'daily' (every morning, default), 'weekly' (Tuesdays after the Gazette), or 'custom' (every scheduleDays days) | daily |
| threshold | No | Minimum risk score to alert on (0.45 = MEDIUM and up, 0.65 = MEDIUM-HIGH and up, 0.85 = HIGH only) | |
| scheduleDays | No | For schedule 'custom': check every N days (2–30) | |
| sessionToken | No | 60-minute watch session token from a previous verification, for the email above | |
| goodsDescription | Yes | What you sell, e.g. 'music streaming app' |