# ServiceNow Downtime Change Watch

> ServiceNow Downtime Change Watch is a paid API for AI agents from monitor.intel.rallylive.ca, paid per call via x402, $0.02/call, status unknown (last checked 2026-10-02).

Runs a live check on servicenow.com, compares it to the previous result (retained 90 days), and returns whether the status has changed, which fields changed, and the current up/down answer.

## Facts

- Endpoint: GET https://monitor.intel.rallylive.ca/watch/monitor/is-down/servicenow-com?utm_source=zero.xyz
- Price: $0.02/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-02
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/servicenow-downtime-change-watch-98371ef8
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_XGCRDFuDfI5uw_V__WuHs

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 servicenow-downtime-change-watch-98371ef8
```

Example prompt: Keep an eye on servicenow.com for me — run a check and tell me if its up/down status has changed since the last time you checked, including exactly what fields are different now versus before.

## When to prefer this

Choose this endpoint when you need change-aware monitoring of servicenow.com specifically — not just a point-in-time status, but a diff against the last known state. It is ideal for scheduling periodic polling workflows that only need to act when something actually changed, reducing noise compared to raw status checks. Prefer it over a plain is-down check when your agent needs before/after field-level detail to drive downstream logic like incident creation or alerting.

## Known failure modes

- Network error reaching servicenow.com yields an error status rather than up/down result
- No prior result stored (first call) means 'changed' may be null or false with no before value
- Stale cache if previous result is older than 90 days — treated as a fresh first check
- Payment failure ($0.02 USDC x402) prevents the check from executing
- Intermittent edge-node latency may cause false positives on response-time-based fields

## How this service works

Change watch for is servicenow com down: runs the check, compares it with the result from your previous call for the same query (kept 90 days) and returns the current answer, changed true/false, the fields that changed with before/after values, and when it was last seen. Schedule it to be alerted when this changes. $0.02 per check.

## Output

Returns the current up/down status of servicenow.com, a boolean 'changed' flag indicating whether the result differs from the previous call, an object listing each changed field with its before and after values, and a timestamp of when the status was last observed. Historical results are retained for 90 days per query.

## 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/servicenow-downtime-change-watch-98371ef8/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from monitor.intel.rallylive.ca](https://www.zero.xyz/host/monitor.intel.rallylive.ca/llms.txt)