Writing a watch
A good watch names one thing and one limit. Use a mint or a wallet address when a ticker could mean several tokens. Any language works.
| You write | The goose watches |
|---|
| the dev of <mint> sells | Creator balance, down 1% from now |
| the largest wallet of $BONK dumps 5% | Largest real wallet, down 5% from now |
| JUP liquidity falls 20% in a day | Liquidity, down 20% within 24 hours |
| this wallet makes any transaction | Newest transaction of the wallet |
| Kamino Lend TVL drops 10% in 24 hours | Solana TVL, down 10% within 24 hours |
The goose always reads the rule back with the live number. Nothing runs until you press Arm it.
What it can see
| Subject | Readings |
|---|
| Token | Price, market cap, liquidity, 24h volume, holders, top holders share, mint authority, freeze authority, creator balance, largest wallet balance |
| Wallet | Balance of any token, SOL balance, any new transaction |
| Protocol | TVL on Solana |
It cannot see tweets, news, sentiment or other chains. Ask for those and it says so before anything starts.
When it fires
- Above or below a number: fires when the reading crosses the line. If it is already past the line when you arm it, the goose waits for the next crossing.
- Falls or rises by a percentage in a window: compares with the oldest reading inside the window. A new watch has a short history until the window fills.
- Falls or rises with no window: compares with the first reading, then counts again from each honk. That is how "the dev sells" catches a second sale.
- Changes: fires on every new value.
- One honk per event: a line or window rule stays quiet until the condition stops being true.
- Missing data: never fires. After six misses in a row the watch shows as blind.
Each watch is read at its interval, so a honk can arrive up to one interval after the event. This is a guard, not a sniper tool.
The report
When a watch fires, the honk lands in your log at once, then the goose looks for the cause with read-only data: balances, transactions, pairs, holders and earlier honks. A report opens with one line on what happened, then the evidence.
Each finding quotes the data it came from, and code compares the quote with that data. Checked means the number came from the source, not that the source is right. Unchecked means the quote did not match, and the finding stays visible with that stamp. If the cause cannot be proved, the report says so. Every step can be opened and read.
Limits
Free wallets keep 2 watches, read every 15 minutes, with 3 investigations a day. See Token for the tiers. Past the daily limit a watch still honks, without the report.
API and MCP
A bot can post the same watches. Every key belongs to a wallet, and its limits follow that wallet's tier.
API key
Connect a wallet to make a key.
MCP tools: watch, my_watches, stop_watch, honks, get_honk.
Public REST: GET /v1/stats, GET /v1/board, GET /v1/honks, GET /v1/honks/:id, GET /v1/metrics.
Gander