AGENTKIT/WORKS

integration · tripwire tier

Wachete Monitor Kit

Turn any agent into a change-detection operator — monitor any webpage, detect diffs, alert on changes. No API key required to start.

PRICE$29$19

One skill file that makes your agent notice when the internet changes. Monitors any public URL for content changes using Wachete API or a zero-config direct HTTP fallback. Works immediately after install — no signup, no API key, just 'monitor this page.' Chains with Zyte (scrape the new content) and Xata (store the diff history).

$ tree wachete-monitor-kit/✓ actual contents
wachete-monitor-kit/
├── README.md                  ← human overview + quick start
├── INSTALL.md                 ← agent reads this to install itself
├── install.json               ← manifest: destinations + verify checks
├── LICENSE                    ← MIT — commercial use OK
├── SPEC.md                    ← (authoring spec, excluded from zip)
├── skills/
│   └── wachete-monitor/
│       └── SKILL.md           ← the skill: API + fallback modes, 6 steps, 7 red flags
├── templates/
│   └── mcp-config.yaml        ← ready-to-paste MCP server block
└── examples/
    └── prompts.md             ← 10 known-good prompts

Why it's different

  • Works immediately with zero config — direct HTTP fallback hashes pages and detects changes
  • Wachete API mode unlocks CSS selectors, change history, and email alerts
  • Pipeline-ready: chains with Zyte (scrape changes) + Xata (store diff history)
  • Ideal for cron jobs — monitor competitor pages, job boards, pricing automatically

Questions, answered

Do I need a Wachete account?+

No. The direct HTTP fallback works immediately — it fetches the page, hashes it, and compares against the last check. A Wachete API key unlocks advanced features (CSS selectors, 30-day history, email alerts) but basic monitoring works with zero signup.

How many pages can I monitor?+

With Wachete's free tier: 5 pages, daily checks. With direct HTTP fallback: unlimited, but respect rate limits — minimum 1 hour between checks per page. The skill enforces this automatically.

What's the pipeline with Zyte and Xata?+

The three kits chain naturally: Wachete detects a change → Zyte scrapes the new content → Xata stores it with a timestamp. One sentence: 'Monitor, scrape, and store' — three kits, one pipeline.