# jp-data-api Watch Check

> jp-data-api Watch Check is a paid API for AI agents from jp-data-api-production.up.railway.app, paid per call via x402, $0.002/call, status unknown (last checked 2026-09-14).

Polls a previously created watch to check whether its trigger condition has fired, returning status, trigger time, and observed value.

## Facts

- Endpoint: GET https://jp-data-api-production.up.railway.app/watch/check
- Price: $0.002/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/jp-data-api-watch-check-c13d343e
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_WlfoPG3h5889NOQKvq5dB

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 jp-data-api-watch-check-c13d343e
```

Example prompt: Has watch abc-12345 triggered yet? If so, what value was observed and when did it fire?

## When to prefer this

Use this endpoint when you have already created a watch via /watch/create and need to poll it to see if its condition has been met. Ideal for cheap, repeated polling of market price thresholds, seismic event thresholds, or corporate filing triggers without setting up a webhook.

## Known failure modes

- Invalid or unknown watchId returns an error response
- Watch not yet triggered returns non-triggered status with no trigger time or value
- Malformed request missing watchId returns validation error
- Payment failure (402) if x402 payment header is missing or insufficient

## How this service works

Check whether a watch created via /watch/create has triggered. Returns status, trigger time, and the observed value. Cheap polling for agents monitoring markets, seismic events, or corporate filings.

## Output

Returns the current status of the watch (triggered or not), the timestamp when it triggered (if applicable), and the observed value that caused the trigger.

## 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",
     "required": [
      "watchId"
     ],
     "properties": {
      "watchId": {
       "type": "string"
      }
     }
    }
   },
   "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/jp-data-api-watch-check-c13d343e/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from jp-data-api-production.up.railway.app](https://www.zero.xyz/host/jp-data-api-production.up.railway.app/llms.txt)