For developers & product teams
Radar-verified storm data,
one REST call.
Hail verified against NOAA MRMS radar, damaging wind against measured NWS storm reports, joined to parcel data — so a request returns storms, or every property under a swath, with no ETL on your side.
100 free credits · no card · public pricing · OpenAPI spec
Integration surface
Five ways in. Same data behind all of them.
REST + OpenAPI
Bearer-auth JSON over HTTPS, metered per call. Spec at /openapi.json — generate a client or point your tooling at it.
MCP connectors
Nine tools in Claude, ChatGPT, or any MCP client. Hosted endpoint with OAuth at /mcp, or run the stdio server yourself.
Webhooks
Register a monitor over a territory; we POST the moment radar verifies a storm inside it. Payload carries storm id, type, severity and a report URL.
SDKs
Typed clients so you're not hand-rolling requests, plus a Zapier app for the no-code side of a customer's stack.
What the data actually is
Verification is the product.
Hail comes from NOAA MRMS radar on a ~2-minute ingest cycle — a measured maximum expected hail size per swath, not a model's guess. Damaging wind comes only from NWS storm reports with a recorded gust or recorded damage. There are no forecasts in the API, and a storm that can't be verified isn't returned.
Honest status
Live component health and measured ingest freshness at /status.json — no fabricated uptime numbers.
Predictable metering
Reports bill one credit per property returned; quote the exact cost before you spend it. Published rates, metered overage, no surprise invoice.
Start
Free key, then 5,000 credits for $29.
The free tier is 100 credits a month with no card, which is enough to build against. Paid tiers start at $29/mo and meter from there.