changedetection.io

Workflows the agent can manage

• watch web pages for changes
• monitor prices or stock
• send change notifications
• track page history

Agent operability

Editorial agent-readiness estimate: 4/5. This reflects documented interfaces and proposed workflows, not a successful installation or a support promise. Assessment date not recorded; verify upstream documentation before use.

• REST — HTTP/API integration is available for automation; re-check current API scope before relying on a specific operation
• WEBHOOKS — Notification targets can include custom HTTP endpoints through the notification system

Evidence consulted

• Official README documents Docker Compose and standalone Docker deployment with persistent /datastore storage. [stated; https://github.com/dgtlmoon/changedetection.io/blob/master/README.md]
• GitHub repository metadata records the project licence as Apache-2.0 and describes self-hosted website change monitoring. [stated; https://github.com/dgtlmoon/changedetection.io]

Implementation notes

Deploy with persistent storage, use the built-in fetcher by default, add browser-backed fetching only where needed, and configure notification destinations without exposing credentials in chat.

Licence / edition: Apache-2.0 Upstream also offers a hosted SaaS service; the open-source self-hosted project remains separately deployable.

Resources: standard class — The upstream project supports a lightweight built-in fetcher and optional browser-backed fetching for JavaScript-heavy pages. Base usage is modest, but browser workers and watch volume can raise CPU/RAM needs, so size from the intended monitoring workload. (inferred)

External prerequisites: notification-provider credentials only for channels that require them

Security: Catalogue qualification is not a security certification; inspect current advisories, supported versions and deployment guidance before setup.