# GitLab.com Downtime Change Watch

> GitLab.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 if GitLab.com is down, compares the result against the previous call (retained 90 days), and returns whether the status changed along with before/after field diffs.

## Facts

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

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 gitlab-com-downtime-change-watch-5f8942a3
```

Example prompt: Keep an eye on GitLab.com for me and let me know if its status has changed since the last time you checked — I need to know right away if it goes down or comes back up.

## When to prefer this

Use this endpoint when you need change detection for GitLab.com specifically — not just a point-in-time status check. It is ideal for polling-based alert workflows where you want to know if something changed between calls rather than just whether the site is up right now. Prefer this over generic ping tools when you need structured before/after diffs and persistent state across calls.

## Known failure modes

- No prior check exists for this query (first call returns no comparison data)
- GitLab.com check itself times out or is unreachable from the monitoring server
- Payment of $0.02 USDC not authorized, resulting in 402 Payment Required
- History older than 90 days is purged, causing comparison loss
- Rate limiting or network errors on the monitoring backend

## How this service works

Change watch for is gitlab 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 GitLab.com, a boolean indicating whether the status changed since the previous call, a diff of which fields changed with before and after values, and a timestamp of when the status was last seen. History is 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/gitlab-com-downtime-change-watch-5f8942a3/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)