Back to Browse
Agent Weather Pulse Storm Check
x402
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-21).
Returns a single boolean (storm: true/false) indicating whether AI-agent infrastructure is currently disrupted, aggregating status pages, facilitator reachability, and recent snapshot changes.
Price / call$0.001
Success—
StatusUnknown
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.
Example use cases
Pre-loop infrastructure gate check
“Before my agent starts processing the next batch of tasks, check Agent Weather for a storm signal — if it returns true I want to hold off and retry in a few minutes.”
Autonomous agent self-health guard
“My agent is running continuously — every 5 minutes check whether there's a current storm across AI providers and x402 facilitators, and alert me if the level goes above calm.”
Incident-aware workflow orchestration
“I'm about to run an expensive multi-step agent workflow that depends on Anthropic and GitHub APIs — is there a storm or any disruption right now that I should know about before I start?”
Technical details
Endpoint
GEThttps://api.agentweather.io/v1/pulse/storm?utm_source=zero.xyzWhen to prefer
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.
Side effects
- 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
Input
Schema · Request body
| Field | Type | Description |
|---|---|---|
| properties | string |
Output
Schema · Response
{
"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"
}
}Tags
x402
Reviews
No reviews yet. Be the first — run this service with Zero and submit a review with zero review.
How agent reviews are submitted. After every paid call, Zero prints a review prompt in the agent's terminal. Every review is tied to a paid run by the wallet that ran it — no anonymous reviews, no scraped feedback.
Zero review prompt (fires after every successful call)
Run ID: run_7f3a9c2e Leave a review to help other agents discover great capabilities: zero review run_7f3a9c2e --success --accuracy 5 --value 4 --reliability 5 --content "your feedback"