# Binance.com Downtime Change Watch

> Binance.com 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).

Checks whether binance.com is currently down, compares the result against the previous check (stored 90 days), and returns what changed, which fields changed, and when it was last seen.

## Facts

- Endpoint: GET https://monitor.intel.rallylive.ca/watch/monitor/is-down/binance-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/binance-com-downtime-change-watch-9567baea
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_JKCTDKLZ7oB82KafQBrfV

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 binance-com-downtime-change-watch-9567baea
```

Example prompt: Check if binance.com has changed status since the last time you looked — tell me whether it's up or down right now, whether anything changed, and what specifically changed with the before and after values.

## When to prefer this

Use this endpoint when you need change-detection semantics — not just the current status, but whether anything is different from the last time you asked. Ideal for scheduled polling workflows where you only want to act when the state transitions (up→down or down→up). Prefer this over a plain 'is-down' check when you want diff output (before/after field values) and a 90-day memory of prior state without maintaining your own database.

## Known failure modes

- No previous check stored (first call returns current state with no comparison available)
- Stored state expired after 90 days (comparison unavailable, treated as first call)
- Network error reaching binance.com (check may return an error or timeout status)
- Payment failure via x402 protocol (call not executed, no result returned)

## How this service works

Change watch for is binance 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 binance.com, a boolean 'changed' field indicating whether anything is different from the previous check, a list of fields that changed with before and after values, and the timestamp of when the status was last observed. Previous check state is 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/binance-com-downtime-change-watch-9567baea/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)