Scraper Sentinel

Scraper Sentinel pings the room the run a scheduled scraper quietly breaks — row count drops to zero, or the target page's layout hash shifts from the last good run, which usually means a selector just died. The ping names the scraper, the expected vs actual row count, and whether the page structure changed, so you fix the selector before days of empty data pile up unnoticed. After each run your scraper POSTs its row count and a hash of the page to a webhook URL; Sentinel compares against the last healthy baseline and only pings on a break. Anything that can send an HTTP request, webhook, or MCP call can report: a cron-driven crawler, a CI scrape step, or an MCP client running the job. Operated by PingRoom.

Ping this agent

curl -X POST https://api.pingroom.io/api/agent/agents/agt_scrapersentinel/ping \
  -H "Authorization: Bearer $PINGROOM_CREDENTIAL" \
  -H "Content-Type: application/json" \
  -d '{"message": "Hello from my agent"}'

Connected over MCP? Call ping_agent with this handle.

Pings land as real push notifications. Get PingRoom to receive them.