America's first AI-native storm intelligence API
Swath API verifies hail against NOAA radar and damaging wind against measured NWS storm reports, fires a webhook the moment a storm crosses your coverage, and returns every affected property — enriched, filtered, and verified. One REST API.
free trial · no card required · one REST API · works inside Claude (MCP)
Verified listings
Reviewed, approved, and published — installable by any Claude organization.
The Model Context Protocol project's canonical server registry (registry.modelcontextprotocol.io) — listed as com.swathapi/swath.
Graded A for tool definition quality and server coherence. MIT licensed.
Two ways in
Ask in plain English which of your counties got hit and which homes are under the swath. Nothing to install, no code, no dashboard to learn.
One REST API over radar-verified hail and wind, plus MCP connectors, SDKs, webhooks and Zapier. Public docs, published pricing, free key in one curl.
Swath CRM · the canvassing platform
Radar-verified hail on a map, every roof under it pinned as a lead. Knock it alone, or run a whole crew from their phones.
ONE REP, ONE PHONE
A WHOLE CREW
$19 per seat per month — annual saves two months. Includes 2,000 storm doors + 300 fresh roof records monthly. Works in any browser; add to home screen for phone push.
Swath Copilot · in your account
Copilot is a chat window inside your Swath account — no API, no dashboard, no setup. Ask in plain English and it runs the same nine tools the API exposes, on your key, answering only from radar-verified results.
Each message costs 10 credits, plus whatever data it fetches — all of it metered in your usage, same as an API call. 50 messages per day. Your free key includes 2 free trial credits — your first storm search on us, everything after is paid.
No code required
Your reps don't need another dashboard. They ask their AI in plain English — and the answers come from radar-verified storm data, metered to your key.
One email field, no card. Your API key comes back instantly with a free trial search to prove the data is real.
/signup →claude.ai → Settings → Connectors → Add custom connector
One URL. Every MCP-capable AI.
CLAUDE IS THE SMOOTHEST PATH — PASTE THE URL AS A CUSTOM CONNECTOR AND TALK. ANY MCP-CAPABLE CLIENT WORKS THE SAME WAY.
All integrations →Ask in plain English — "which roofs in my territory took hail over 1.5 inches?" — and get answers backed by radar, not rumors.
Three REST endpoints and the Swath Report. Build storm mode into your product in an afternoon.
Read the docs →A storm crosses your territory → a signed POST hits your endpoint within minutes of radar verification. No polling.
Not a developer? Turn on email alerts and get the same storm notice in your inbox.
EVERY PROPERTY RECORD CARRIES
WHAT WE DELIBERATELY LEAVE OUT
The pipeline
Each endpoint stands alone. Together they take you from a radar echo to a ranked list of the roofs it hit.
Register your service area as a polygon. When NOAA MRMS radar confirms hail or damaging wind inside it, a webhook fires within minutes — with the storm cell, severity, and swath geometry attached.
One address in, one typed record out: year built, square footage, estimated roof age, owner-occupancy, assessed value. Every record says which source each field came from. Cached and normalized from county assessor and parcel data.
Query every verified event — by bounding box, time window, hail or wind. Each row carries measured severity and a swath ID that unlocks the geometry and the full property list.
The flagship call
The join is the product. One call turns a verified storm into a filtered target list — the exact output every roofing CRM, restoration platform, and lead desk is paying for today.
{
"storm_id": "sw_8c14",
"type": "hail",
"mesh_max_in": 1.75,
"verified_at": "2026-07-18T21:44:00Z",
"total": 4211,
"data": [
{
"address": "4012 NW 72ND AVE, CORAL SPRINGS, FL",
"year_built": 1999,
"roof_age_est": 17,
"roof_material": "asphalt_shingle",
"owner_occupied": true,
"exposure": { "hail_in": 1.6, "score": 0.3 }
},
… 4,210 more
]
}
AI-native in practice
Works today in Claude and ChatGPT — no dashboard, no new tab. Connect yours →
Free tool
Radar-verified storm history for any US address. No login, no forecasts — measured events only.
Live everywhere
Every verified storm, posted the moment it happens — the same cards the bot ships to the feed. Follow @SwathAPI for live storm calls, or catch the same feed on Telegram, Discord, and Bluesky.
The Daily Swath
Free — the same map and stats the pros pull, one email every morning.
How it works
A cell enters a polygon you registered — a county, a metro, or every roof your customers serve.
We confirm hail size and wind speed against the MRMS national feed on its 2-minute cycle. No forecasts, no rumors — measured events only.
Storm cell, severity, and swath geometry arrive at your endpoint while competitors are still watching the news.
Request every affected parcel, filtered and scored. Enrich single addresses on demand. Bill your customers on the result.
Who builds on Swath
You integrate once; your users get storm intelligence under your brand. Swath stays invisible.
Built for the agent era
Every endpoint is exposed as an MCP server — paste /mcp?key=sk_… into Claude as a custom connector — and agents can self-serve credentials from a machine-readable auth guide. Tell your coding agent to "add storm triggers" — it does the rest.
$ claude "wire storm alerts into our CRM" → Found /agents.md → Registered API key sk_… → Created monitor SOFL-COVERAGE-01 → Webhook handler added · tests passing Done in 4m 12s.
Launch pricing
Every plan is a monthly credit allowance — a Swath Report bills 1 credit per property returned (+25 per fresh-fetched record, 10-credit minimum), a property lookup 2, everything else 1. Failed requests are never billed.
LAUNCH PRICING — LOCKED FOR EARLY ACCOUNTS · NEED MORE, SSO, OR AN MSA? → BUILD@VIBECODEBEAST.COM
Partners
Refer restoration-tech teams and earn a cut of every invoice they pay. Free to join, no approval queue.
Straight answers
Hail events are derived from NOAA's MRMS national radar network on its live 2-minute cycle — the same measured data the insurance industry underwrites against. Wind events come from measured NWS gust and damage reports on the ground. We never trigger on forecasts.
County assessor and public parcel data, normalized into one schema and cached. Records refresh on lookup when stale. Roof age is an estimate derived from year built — every record carries a roof_age_source field so you always know which input produced it. Permit-derived roof ages are on the roadmap, not in the data today.
No — deliberately. Swath returns the property: address, year built, square footage, roof-age estimate (from year built), owner-occupancy (inferred from the assessor mailing address), assessed value, and the hail size measured at that location. We don't sell homeowner names, phone numbers, or emails — you know exactly which roofs took the hit, and you choose how to reach the people under them in line with the rules that apply to your outreach (see the Terms).
Storm type, measured severity (MESH hail size or wind speed), the verification timestamp, and URLs for the swath geometry (GeoJSON) and the full Swath Report. Delivery is HMAC-signed, retried with backoff, and exactly-once per storm and monitor.
A Swath Report bills 1 credit per property returned (10-credit minimum) plus 25 credits per record fetched fresh from the parcel vendor — preview the cost with the 1-credit quote endpoint. A single-property lookup is 2 credits, every other call is 1. Failed requests are never billed. Paid plans meter overage past the monthly allowance; the Free plan hard-stops at 100 — enough to integrate and evaluate the full pipeline.
Yes — that's the point. Swath is white-label infrastructure: your users see your brand, your UI, and your pricing while we meter usage behind the scenes. One limit — raw parcel records can't be resold as a standalone dataset (see the Terms).
Be the platform that knows first. Integration takes an afternoon — or hand it to your agent and take the afternoon off.
