# AgentCron URL Watch Registration

> AgentCron URL Watch Registration is a paid API for AI agents from cron.memoryapi.org, paid per call via x402, $0.01/call, status unknown (last checked 2026-09-15).

Registers a URL with AgentCron to be polled on a specified interval, creating change alerts when the response content changes.

## Facts

- Endpoint: GET https://cron.memoryapi.org/x402/cron/watch
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/cron-memoryapi-org-3acb0d3e
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_O3zDdopypxpcnh2CNu4HT

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability cron-memoryapi-org-3acb0d3e
```

Example prompt: Keep an eye on https://status.example.com and alert me whenever the response changes — check it every 5 minutes.

## When to prefer this

Use this endpoint when you need to proactively detect changes to a remote URL on a recurring schedule without building your own polling infrastructure. Ideal for monitoring API responses, status pages, data feeds, or any web resource where change detection matters to downstream workflows.

## Known failure modes

- Invalid or unreachable URL returns an error
- Unsupported polling interval format causes rejection
- Missing required URL parameter returns 400 error
- Payment failure via x402 protocol prevents registration
- Duplicate registration may return conflict or existing monitor ID

## How this service works

Register a URL to monitor for changes. AgentCron polls it on your interval and creates alerts when the response changes.

## Output

A confirmation that the URL has been registered for monitoring, likely including a watch/monitor ID, the registered URL, and the polling interval that was set. This ID can then be used to retrieve alerts when changes are detected.

## Example request

```json
{
 "url": "https://httpbin.org/status/200",
 "notify": "zero-qa@agentmail.to",
 "interval": "5m"
}
```

## Request schema (JSON Schema)

```json
{
 "properties": {
  "input": {
   "required": [
    "method"
   ],
   "properties": {
    "method": {
     "enum": [
      "GET"
     ],
     "type": "string"
    }
   }
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "url",
  "message",
  "success",
  "watcher_id",
  "check_interval_minutes"
 ],
 "properties": {
  "url": {
   "type": "string"
  },
  "message": {
   "type": "string"
  },
  "success": {
   "type": "boolean"
  },
  "watcher_id": {
   "type": "string"
  },
  "check_interval_minutes": {
   "type": "number"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/cron-memoryapi-org-3acb0d3e/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from cron.memoryapi.org](https://www.zero.xyz/host/cron.memoryapi.org/llms.txt)