Ayewatch
AyeWatch monitors public-web topics and individual pages for meaningful changes. You can describe a company, question, or event to follow, or paste a URL for a product page or careers site. Its official monitoring page explains the setup, alert channels, and schedules, including an adaptive Auto mode on paid plans.
Choosing a topic and check schedule
You can start from a template, write a topic description, or paste a webpage link. AyeWatch lets you add the conditions that matter, such as a target price or a particular job role. The template gallery includes price drops, job openings, product releases, and company monitoring, among other subjects.
Each monitor has its own schedule. Auto monitoring speeds up while a topic is busy and slows down when it is quiet. Custom scheduling lets you select an interval within the limits of your plan, with Daily or slower intervals on Free Preview. You can edit or pause a topic after creating it.
Receiving updates and checking evidence
Updates appear in a feed with summaries and supporting source links. Every plan includes push notifications and the in-app feed. Paid plans add email, Slack, Discord, and webhooks, as well as a daily digest email. AyeWatch works on the web, iOS, and Android, with topics and alerts synchronized across those platforms.
The free preview includes three lifetime monitoring runs across up to three topics. Those runs do not renew, and no credit card is required. Each completed monitoring check uses one credit; the account shows the balance and refill date, while topic scheduling shows estimated credits per day.
Connecting applications and AI assistants
Paid plans include a REST API for managing topics and an MCP connection through which an assistant can create, change, or pause monitors. That connection requires an AyeWatch API key.
The webhook documentation says events are sent only when new content is detected. Receivers must accept HTTPS POST requests and return a successful response within ten seconds. Failed deliveries can be retried up to ten times, so the documentation recommends idempotent handlers. Requests carry an HMAC-SHA256 signature that should be verified against the raw body before processing. This provides a documented path for sending updates into an existing application.