# Monitor changes to a public web standards page

**Use case:** 

Use Signal Foundry's website monitor on the W3C standards page. Inspect the content hash and change status, then repeat later to detect normalized text changes. The first observation establishes a baseline. Replace the URL with a permitted public server-rendered page. No visual diff or JavaScript rendering.

## Input

```json
{
  "urls": [
    "https://www.w3.org/standards/"
  ]
}
```

## Output

```json
{
  "url": {
    "label": "Url",
    "format": "string"
  },
  "changed": {
    "label": "Changed",
    "format": "boolean"
  },
  "content_hash": {
    "label": "Content hash",
    "format": "string"
  },
  "content_bytes": {
    "label": "Content bytes",
    "format": "integer"
  }
}
```

## About this Actor

This example demonstrates how to use [Website Change Monitor and Hash Checker](https://apify.com/signal-foundry/website-change-monitor.md) with a specific input configuration. Visit the [Actor detail page](https://apify.com/signal-foundry/website-change-monitor.md) to learn more, explore other use cases, and run it yourself.


## How to integrate an Actor?

This Task's input is already configured above. Use it as-is rather than inventing a new one.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For full API examples (JavaScript, Python, CLI, MCP, OpenAPI), see this Task's Actor page: https://apify.com/signal-foundry/website-change-monitor.md

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).