# Vibe Springs Watch Register

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

Registers a conditional watch/alert that monitors a data condition and returns a watch ID for later polling

## Facts

- Endpoint: DELETE https://vibesprings.net/api/watch/register
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-13
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/vibe-springs-watch-register-1d3b4a25
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_SGmReYCXXmIU35tRx1eSf

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-register-1d3b4a25 -d '<json body>'
```

Example prompt: Set up a watch on Vibe Springs that triggers when the air quality index in Los Angeles exceeds 150, and give me the watch ID so I can check back on it.

## When to prefer this

Use this endpoint when you need to set up a persistent, pollable condition monitor against any of the Vibe Springs data services (weather, air quality, earthquakes, marine, flood, solar, crypto, etc.) rather than making one-off queries. Prefer this over direct data endpoints when you want to watch for threshold crossings or state changes over time without continuous polling yourself — the watch system handles the condition evaluation and you simply check the returned endpoint.

## Known failure modes

- Missing or malformed 'condition' field returns validation error
- Missing 'notify' field may cause incomplete registration
- Duplicate watch conditions may return reused:true with an existing watchId
- Invalid condition syntax may return a 400 bad request
- Network timeout if the registration service is temporarily unavailable

## How this service works

Register a watch condition for real-time monitoring of price, gas, weather, wallet, or custom endpoint.

## Output

Returns a JSON object containing a unique watchId (e.g. 'w_1234abcd'), a checkEndpoint URL for polling the watch status, and a 'reused' boolean indicating whether an identical watch already existed and was returned instead of creating a new one.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "notify": {
   "type": "string"
  },
  "condition": {
   "type": "string"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "reused": false,
  "watchId": "w_1234abcd",
  "checkEndpoint": "https://vibesprings.net/api/watch/check?id=w_1234abcd"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/vibe-springs-watch-register-1d3b4a25/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)