# Vibe Springs Watch Condition Check

> Vibe Springs Watch Condition Check is a paid API for AI agents from vibesprings.net, paid per call via x402, $0.008/call, status unknown (last checked 2026-09-14).

Checks whether a previously registered watch condition has triggered, returning the trigger status and updating the caller's baseline.

## Facts

- Endpoint: GET https://vibesprings.net/api/watch/check
- Price: $0.008/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/vibe-springs-watch-condition-check-330272b4
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_gruGPVm6hByTay-LpLoNO

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 vibe-springs-watch-condition-check-330272b4
```

Example prompt: Check if my Vibe Springs watch with ID 'wch_abc123' has triggered yet.

## When to prefer this

Use this endpoint when you have already registered a watch condition via vibesprings.net's register endpoint and need to poll it to detect whether the condition has been met. Prefer this over re-registering a watch or using a general data endpoint when you want incremental, stateful monitoring with automatic baseline advancement.

## Known failure modes

- Missing or invalid watchId returns a 400 or error response
- Watch ID not found or expired returns a 404-style error
- Payment failure (x402) if USDC balance is insufficient
- Rate limiting if polled too frequently
- Network timeout or server error returning a 500-level response

## How this service works

Check a watch condition by ID, returning whether it triggered and updating the caller-specific baseline.

## Output

Returns whether the specified watch condition has triggered (boolean or status indicator), along with an updated baseline for the caller so subsequent polls reflect only new changes since this check.

## 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": [
      "id"
     ],
     "properties": {
      "id": {
       "type": "string",
       "description": "The unique watchId returned by the register endpoint."
      }
     }
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "type": "object"
    }
   }
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "kind": "price",
  "delta": null,
  "target": "BTC-USD",
  "watchId": "w_1234abcd",
  "checkedAt": 1782800000000,
  "triggered": false
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/vibe-springs-watch-condition-check-330272b4/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from vibesprings.net](https://www.zero.xyz/host/vibesprings.net/llms.txt)