# latency-probe-watch

> latency-probe-watch is a paid API for AI agents from intel.rallylive.ca, paid per call via x402, $0.02/call, status unknown (last checked 2026-09-14).

Runs a latency probe check against a URL and returns whether the result has changed since the previous call, including field-level before/after diffs, retained for 90 days.

## Facts

- Endpoint: GET https://intel.rallylive.ca/watch/monitor/latency
- Price: $0.02/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/latency-probe-watch-fcd8e3bc
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_Dl_ha22dWZccONlSJOMDK

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 latency-probe-watch-fcd8e3bc
```

Example prompt: Keep an eye on the latency probe for https://example.com using a GET request and let me know if anything has changed since the last time you checked — show me exactly which fields changed and what the before and after values were.

## When to prefer this

Choose this endpoint when you need to detect changes in latency probe results over time rather than just fetching the current value. It is ideal for scheduled monitoring workflows where you want field-level diffs and before/after values automatically, without building your own state management. Use it instead of a raw latency probe when you need 'has anything changed?' semantics backed by a 90-day history store.

## Known failure modes

- URL is unreachable or returns non-2xx, resulting in an error or a latency probe failure state
- No previous result stored (first call for a URL), so 'changed' may be null or false with no diff
- Result older than 90 days is purged, causing the comparison baseline to be missing
- Invalid or malformed URL input causes a schema validation error
- Rate limiting or payment failure ($0.01 per check) blocks the request

## How this service works

Change watch for latency probe: runs the check and compares it with the result from your previous call for the same url (kept 90 days), returning the current answer, changed true/false, exactly which fields changed with before/after values, and when it was last seen. Call it on a schedule to be told when latency probe changes. $0.01 per check.

## Output

Returns the current latency probe result, a boolean 'changed' flag indicating whether the result differs from the previous call for the same URL, a field-level diff listing exactly which fields changed along with their before and after values, and a timestamp of when the previous result was last seen. Historical results are retained for 90 days.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "required": [
  "input"
 ],
 "properties": {
  "input": {
   "type": "object",
   "required": [
    "type",
    "method"
   ],
   "properties": {
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "GET"
     ],
     "type": "string"
    },
    "queryParams": {
     "type": "object",
     "properties": {}
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "type": "object"
    }
   }
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/latency-probe-watch-fcd8e3bc/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from intel.rallylive.ca](https://www.zero.xyz/host/intel.rallylive.ca/llms.txt)