# Vibe Springs Watch Batch Check

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

Checks the status or data for a batch of up to 5 watch IDs concurrently, returning inline results for each.

## Facts

- Endpoint: GET https://vibesprings.net/api/watch/check-batch
- Price: $0.02/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-batch-check-08aae383
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_abwm8_iAzUXiFE1-RqG8a

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-batch-check-08aae383
```

Example prompt: Can you check the status of these five watches on Vibe Springs at once — IDs watch_001, watch_002, watch_003, watch_004, and watch_005 — and tell me the inline result for each?

## When to prefer this

Use this endpoint when you need to check multiple watch IDs (up to 5) in a single call rather than making separate sequential requests. Ideal for agents that want low-latency, concurrent batch lookups of watch data without orchestrating multiple individual calls.

## Known failure modes

- More than 5 IDs submitted — API only supports up to 5 per batch call
- Malformed or missing 'ids' query parameter — returns validation error
- One or more watch IDs not found — may return partial results or per-ID error
- Payment not completed (x402 protocol failure) — request not processed
- Network timeout on concurrent lookup — may return partial or empty results

## How this service works

Check a batch of up to 5 watches concurrently, returning inline results for each ID.

## Output

Returns a set of inline results for each submitted watch ID, including status or relevant data per watch, all returned concurrently in a single response.

## 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": [
      "ids"
     ],
     "properties": {
      "ids": {
       "type": "string",
       "description": "Comma-separated list of up to 5 watch IDs to check"
      }
     }
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "type": "object"
    }
   }
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "results": [
   {
    "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-batch-check-08aae383/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)