# MongoDB.com Uptime Change Watch

> MongoDB.com Uptime 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 if mongodb.com is currently down, compares the result with the previous check (stored for 90 days), and returns whether the status has changed along with before/after field diffs.

## Facts

- Endpoint: GET https://monitor.intel.rallylive.ca/watch/monitor/is-down/mongodb-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/mongodb-com-uptime-change-watch-51bdd5a8
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_Pz-86VYq5E3WjVyMicppl

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 mongodb-com-uptime-change-watch-51bdd5a8
```

Example prompt: Keep an eye on mongodb.com for me — call the change watch endpoint periodically and let me know as soon as its up/down status changes from what it was last time.

## When to prefer this

Choose this endpoint when you need change-detection semantics specifically for mongodb.com — i.e., you want to know not just the current status but whether it differs from the last known state. Ideal for scheduling periodic alerts that fire only on transitions (up→down or down→up) rather than every poll. Prefer over a plain is-down check when you want to avoid redundant notifications during a prolonged outage.

## Known failure modes

- If no previous check exists for the query, 'changed' may be undefined or the first call is treated as a baseline with no diff
- Network timeout reaching mongodb.com from the edge checker results in an error status
- Payment of $0.02 USDC not completed causes request rejection
- Stale cache beyond 90 days results in loss of comparison baseline

## How this service works

Change watch for is mongodb 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 answer for mongodb.com, a boolean 'changed' flag indicating whether the result differs from the previous call, a diff of which fields changed with their before and after values, and a timestamp of when the status was last observed. Previous results are retained for 90 days for comparison.

## 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/mongodb-com-uptime-change-watch-51bdd5a8/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)