Web Page Change Monitor
ivy.agent.page-change-materiality · v1.0.0
ivyx
Fetch a web page, detect text changes, evaluate significance with Jev, and email the new content if significant.
Steps
In the order the agent's file lists them. A branch or a loop is a step too; the wiring between steps is in the file.
- 01Ivy NodeWeb Page Textivy.node.web-page-text
- 02Ivy NodeJev · Noulivy.node.jev-noul
- 03Branchonly if the change matters
- 04Ivy NodeEmail Sendivy.node.email-send
Nodes it brings
Adding this agent in IVYX Studio adds these nodes with it. A node your workspace already has is kept as it is, even at another version.
What it touches
Collected from what each of its nodes declares, plus the model call when a step is a model turn. A declaration is the author's statement, and it is what policy rules select on.
What it needs
- A stored secret named
jev-api-key. The agent's file carries the name, never the value.
Inputs
| Field | Type | Description |
|---|---|---|
| urlrequired | string | The page's address. |
Outputs
| Field | Type | Description |
|---|---|---|
| title | string | The page title. |
| status | integer | The HTTP status. |
| url | string | The address after redirects. |
| noul | number | The probability that the answer is yes, 0 to 1. |
| answer | boolean | True when noul reaches the threshold. |
| threshold | number | The threshold used. |
| model | string | The model version that answered. |
| sent | boolean | True once the server accepted the message. |
| recipients | array | The addresses it was accepted for. |
| subject | string | The subject sent. |
Tests
1 of 1 test cases passed on Oct 2, 2026, in the publisher's own environment, before this version was published. The registry keeps that record; it does not run the cases again.
Requires: the stored secret jev-api-key, a page served on http://127.0.0.1:18900, a local SMTP relay on port 1025, python:3.9
- status-page
The status page is fetched and Jev judges whether a change matters.