# 2s.io Watcher Status

> 2s.io Watcher Status is a paid API for AI agents from 2s.io, paid per call via x402, $0.0025/call, status unknown (last checked 2026-09-15).

Returns the current status of a crypto-address-activity watcher by its ID, including state, delivery history, and any undelivered events.

## Facts

- Endpoint: GET https://2s.io/api/watchers/status
- Price: $0.0025/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/2s-io-watcher-status-7a0c5cc4
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_zQhDD4xtuVEhk3H-KBjEI

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 2s-io-watcher-status-7a0c5cc4
```

Example prompt: Check the status of my 2s.io watcher with ID 'wch_abc12345' — I want to know if it's still armed, how many fires are left, and whether any callbacks failed to deliver.

## When to prefer this

Use this endpoint when you need to verify the status of an existing crypto-address-activity watcher, check delivery history, or recover any events that were not successfully pushed via webhook. This is the pull-based backstop for missed push notifications — prefer it whenever you suspect a callback was missed or want to audit delivery attempts.

## Known failure modes

- watcherId not found or invalid — returns 404 or error response
- watcherId too short (< 8 chars) or too long (> 80 chars) — schema validation error
- Watcher belongs to a different account — unauthorized error
- Network timeout or service unavailable — 5xx response

## How this service works

Status of a watcher by watcherId: state (armed/completed/expired/cancelled), fires used/remaining, expiry, recent deliveries (with HTTP result + attempt count), and any UNDELIVERED events with their full callback bodies — the pull backstop, so a missed push is always recoverable here. Pairs with watchers.crypto-address-activity.

## Output

Returns the watcher's current state (armed/completed/expired/cancelled), number of fires used and remaining, expiry timestamp, a list of recent deliveries with HTTP result codes and attempt counts, and full callback bodies for any UNDELIVERED events that were not successfully pushed.

## 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",
    "queryParams"
   ],
   "properties": {
    "type": {
     "const": "http"
    },
    "method": {
     "const": "GET"
    },
    "queryParams": {
     "type": "object",
     "required": [
      "watcherId"
     ],
     "properties": {
      "watcherId": {
       "type": "string",
       "maxLength": 80,
       "minLength": 8
      }
     },
     "additionalProperties": false
    }
   }
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/2s-io-watcher-status-7a0c5cc4/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from 2s.io](https://www.zero.xyz/host/2s.io/llms.txt)