# StatePulse Weather Anomaly Detection

> StatePulse Weather Anomaly Detection is a paid API for AI agents from statepulse-api.hahavoid0.workers.dev, paid per call via x402, $0.03/call, status unknown (last checked 2026-09-14).

Detects weather temperature anomalies for a location by comparing current temperature against historical mean and returning deviation metrics with confidence scoring

## Facts

- Endpoint: POST https://statepulse-api.hahavoid0.workers.dev/weather/anomaly
- Price: $0.03/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/statepulse-weather-anomaly-detection-3e577610
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_SWBF5JMShZUOaZEiKoS9f

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 statepulse-weather-anomaly-detection-3e577610 -d '<json body>'
```

Example prompt: Check if the temperature in Miami right now is anomalous — is it significantly above or below the historical average, and how confident are you in that assessment?

## When to prefer this

Use this endpoint when you need to determine whether current temperature conditions at a location are statistically unusual compared to historical norms, especially when a confidence score and deviation percentage are required. Prefer over generic weather APIs when the goal is anomaly detection rather than simple current conditions or forecasting.

## Known failure modes

- Location not supported — 'supported: false' returned with no anomaly data
- Insufficient historical data for reliable comparison — low confidence score returned
- Invalid or unrecognizable location input — 400 error or empty result
- Network timeout to upstream weather data source — 503 or gateway error
- Payment failure via x402 — 402 Payment Required before data is returned

## How this service works

Compares current weather conditions with a 10-year historical average to flag climate anomalies.

## Output

Returns a JSON object with anomaly_status (e.g. 'above_average'), current temperature in Celsius, the historical mean temperature in Celsius, the deviation percentage from the norm, whether the location is supported, and a confidence rating (e.g. 'high').

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "result": {
   "anomaly_status": "above_average",
   "current_temp_c": 24.2,
   "deviation_percentage": 15.2,
   "historical_mean_temp_c": 21
  },
  "supported": true,
  "confidence": "high"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/statepulse-weather-anomaly-detection-3e577610/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from statepulse-api.hahavoid0.workers.dev](https://www.zero.xyz/host/statepulse-api.hahavoid0.workers.dev/llms.txt)