Record your varroa treatments and inspections. A fixed rules table tells you when you are repeating the same active group (the one thing resistance guidance says to avoid), when a label withdrawal period conflicts with your harvest, and when monitoring is overdue. No AI, no guessing — the same records always give the same answer.
| Check | Based on |
|---|---|
| Same active group repeated back to back | IRAC mode-of-action groups (amitraz=19, tau-fluvalinate/flumethrin=3A, coumaphos=1B) |
| Label withdrawal period vs your harvest date | the number you read off your own label — we never invent one |
| Persistent acaricide recorded with honey supers on | published rotation guidance for "hard" acaricides |
| Monitoring overdue | guidance asks for monitoring "at least four times a year" |
| What to use next | the active group you have used least, and not the one you just used |
Every finding names the primary source it comes from. Where a judgment needs a number only your label has, it says "cannot be checked" instead of inventing a value.
One anonymous check per day, no key. Paste this and see the engine answer:
curl -s "https://hive-ledger.rowb.app/api/check-rotation?treatments=%5B%7B%22date%22%3A%222026-04-10%22%2C%22product%22%3A%22apivar%22%7D%2C%7B%22date%22%3A%222026-09-05%22%2C%22product%22%3A%22apistan%22%7D%2C%7B%22date%22%3A%222026-09-20%22%2C%22product%22%3A%22amitraz%22%7D%5D"
Recommended next step. An email address is all it takes, and the same key keeps working if you ever move to a paid plan. Your hive records stay private to your key.
The same engine is an MCP server: https://hive-ledger.rowb.app/mcp — tools check_rotation,
list_active_groups, get_thresholds.
Built for people who keep bees, not for people who sell AI. Part of rowb.app.