Use case · Website monitoring
A website change detection API that understands intent. Instead of raw diffs, you describe the signal — a price drop, a stock flip, a competitor's pricing page edit — and Meerkat's agent watches on a schedule. It only fires your webhook when the described change actually happens.
Plain-English conditions like 'price under $99' or 'plan name changed'. No selectors to maintain.
Headless browser rendering means SPAs, React, and dynamic content work out of the box.
Cron strings, natural language ('every 15 minutes'), or on-demand POST /tasks/:id/run.
Same REST API. Run it on Docker, Fly.io, Render — or use Meerkat Cloud with BYOK.
Example request
curl -X POST https://meerkatagents.com/api/v1/tasks \
-H "Authorization: Bearer mk_live_..." \
-d '{
"task_type": "recurring",
"description": "Notify me when this product drops below $99",
"input_params": {
"url": "https://shop.example.com/widget-pro"
},
"frequency": "every 30 minutes",
"output_webhook": "https://your-app.com/hook"
}'
FAQ
Anything an LLM agent can see — price drops, stock status, copy edits, new blog posts, regulatory text updates, competitor pricing pages. You describe the signal in English; Meerkat watches for it.
Raw-diff tools fire on every cosmetic change. Meerkat understands semantic intent — 'tell me when the price drops below $99' — and only POSTs when that condition is met.
Yes. The agent renders pages in a headless browser before reasoning, so React, Vue, and SPA-rendered content work the same as static HTML.
Meerkat respects robots.txt, throttles per-domain, and reuses cached fetches across tasks targeting the same URL.
Sign up, connect your LLM key in onboarding, and register a task in under five minutes.