Back to Browse
Status State API – Cloudflare Monitor
x402
Status State API – Cloudflare Monitor is a paid API for AI agents from status-state-api.replit.app, paid per call via x402, $0.01/call, status unknown (last checked 2026-10-12).
Returns the current normalized status of Cloudflare, including overall health, fault-first component list, and any active or recently closed incident.
Price / call$0.01
Success—
StatusUnknown
How this service works
Current normalized overall status, fault-first components, active incident (or closedIncidentSummary if stale), and poll clocks. overallStatus and hasActiveIncident are in the 402 JSON body so you can decide whether to pay. $0.01 per call in USDC on Base or Solana, verified and settled by the PayAI facilitator - no API key, no signup.
Output
A JSON object containing: the vendor slug and name, a normalized overallStatus string (e.g. 'operational', 'degraded', 'outage'), a fault-first ordered array of components with their statuses, an activeIncident object (or null if none), a closedIncidentSummary if the most recent incident just closed, timestamps for lastCheckedAt and sourceUpdatedAt, a staleness object, and the checkIntervalMinutes poll clock.
Example use cases
Cloudflare outage alert during deployment
“Before I deploy, can you check if Cloudflare is fully operational right now — are there any active incidents or degraded components I should know about?”
Automated status dashboard refresh
“Pull the latest Cloudflare status including any ongoing incidents and which components are affected, so I can update the team dashboard.”
Incident post-mortem research
“Was there a recent Cloudflare incident that just closed? Can you grab the summary including what components were affected and when it was resolved?”
Technical details
Endpoint
GEThttps://status-state-api.replit.app/api/monitors/cloudflare?utm_source=zero.xyzWhen to prefer
Choose this endpoint when you need a normalized, structured view of Cloudflare's current operational status without scraping or parsing Cloudflare's native status page yourself. It is ideal for agents that need machine-readable status signals to gate deployments, trigger alerts, or update dashboards. Prefer it over raw status page scraping because it provides fault-first component ordering, active incident detection, and poll clocks in a consistent schema. It requires no API key — only a $0.01 USDC micropayment per call via x402.
Side effects
- Slug not found – if 'cloudflare' is not in the monitored catalog, returns an error indicating no matching monitor
- Stale data – if the upstream Cloudflare status page has not updated recently, the staleness field will indicate lag and closedIncidentSummary may be returned instead of activeIncident
- Payment failure – if the x402 USDC payment on Base or Solana is not confirmed by the PayAI facilitator, the call is rejected
- Rate limiting – excessive polling may be throttled by the API
- Upstream unavailability – if the status-state-api.replit.app service itself is down, no response is returned
Input
Schema · Request body
| Field | Type | Description |
|---|---|---|
| inputrequired | object | |
| output | object |
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"