# Agent Weather Pulse Storm Check

> Agent Weather Pulse Storm Check is a paid API for AI agents from api.agentweather.io, paid per call via x402, $0.001/call, status unknown (last checked 2026-10-17).

Returns a single boolean (storm: true/false) indicating whether AI-agent infrastructure is currently disrupted, aggregating status pages, facilitator reachability, and recent snapshot changes.

## Facts

- Endpoint: GET https://api.agentweather.io/v1/pulse/storm?utm_source=zero.xyz
- Price: $0.001/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-17
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/agent-weather-pulse-storm-check-fd621ffc
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_XS9YW7W0FKb6jlrafRamm

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 agent-weather-pulse-storm-check-fd621ffc
```

Example prompt: Before I kick off my next agent loop, quickly check whether there's an infrastructure storm right now — any AI provider outages, facilitator issues, or active fronts that could disrupt things?

## When to prefer this

Choose this endpoint when you need the cheapest, fastest boolean go/no-go on AI infrastructure health before committing an agent loop or expensive workflow. It is purpose-built for tight agent loops where you want a single yes/no rather than a detailed multi-provider breakdown — prefer the full pulse snapshot endpoint when you need per-provider granularity or historical trends.

## Known failure modes

- Network unreachability returns HTTP error with no JSON body
- Stale data if upstream status pages are delayed — asOf timestamp will reflect lag
- Third-party status pages may be wrong or late — noted in notice field
- Deprecated provider keys (openai, cursor) return null values until removal date
- Payment failure if x402 USDC balance is insufficient for $0.001 call

## How this service works

Use when an agent loop needs a cheap yes/no on whether AI-agent infrastructure is disrupted right now. Tiny loop-friendly combined reading: the worst current level across tracked public status pages, our measured facilitator reachability and recent changes in our record. Returns storm (boolean) and…

## Output

Returns a JSON object with: storm (boolean — true if any tracked signal is at storm level), level (string enum: calm, breezy, unsettled, or storm), asOf (ISO timestamp of the reading), reason (human-readable explanation), signal breakdown per source (providers status pages, facilitator reachability, fronts snapshot), schema_version, and a notice about third-party data provenance.

## Request schema (JSON Schema)

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

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "asOf": "2026-10-12T02:30:02.000Z",
  "level": "calm",
  "storm": false,
  "method": "level = worst of: tracked public status pages (critical=storm, major=unsettled,…",
  "notice": "Recorded measurements. Third-party status data is provided as is, may be late o…",
  "reason": "no provider incidents, facilitator ok, no fronts",
  "signal": "storm",
  "sources": [
   {
    "signal": "providers",
    "sources": [],
    "observed_at": "2026-10-12T02:34:12.093Z"
   }
  ],
  "deprecated": {
   "keys": [
    "openai"
   ],
   "note": "providers.openai and providers.cursor are no longer measured and always return …",
   "until": "2026-11-12"
  },
  "schema_version": "pulse-0.2.0"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/agent-weather-pulse-storm-check-fd621ffc/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.agentweather.io](https://www.zero.xyz/host/api.agentweather.io/llms.txt)