POST an address. Get back a graded peril profile with full provenance. Streaming, batch, and webhook variants for production scale.
Returns 54 peril grades + dominant peril analysis + 16-day GFS forecast + sub-hour HRRR forecast for any U.S. address. Cold p50 ~10 ms, p95 ~50 ms.
# Request GET /v1/risks/fast?lat=25.79&lng=-80.13 Authorization: Bearer $KEY # Response · 200 OK { "address_id": 8392104, "address": "1242 Ocean Dr, Miami Beach, FL 33139", "peril_grades": { "hurricane": "F", "storm_surge": "E", "flood": "V", "wind": "D", "hail": "B", "tornado": "C", "wildfire": "A", "earthquake": "A" }, "dominant_peril": "hurricane", "forecast": { "hrrr_sub_hour": { "active_threat": false }, "gfs_16_day": { "max_severity": "moderate" } }, "model": { "version": "AEPM v2024.3", "layers": ["atmos", "surface", "convective", "seismic"] } }
Single-call bulk endpoint backed by a single SQL LATERAL JOIN. ~6 ms per address server-side. Chain calls for any book size.
# Request POST /v1/risks/batch_fast Authorization: Bearer $KEY Content-Type: application/json { "addresses": [ { "lat": 25.79, "lng": -80.13 }, { "lat": 37.78, "lng": -122.41 } ] } # Response { "results": [ /* per-address peril grades */ ] }
Every peril, every sub-extractor, every property indicator, every forecast layer. Heavier and slower than /risks/fast; use for deep audit and one-off enrichment workflows. Redis-backed response cache (1 h TTL).
Cryptographic receipt for any prior response: content SHA-256, Merkle root over the model layers used, Ed25519 signature, signing pubkey. Verifiable offline. Audit-grade.
Returns service uptime, model version, and the calibration vintage in use for each peril layer.
API keys via Authorization: Bearer header. OAuth 2.0 client credentials and mTLS available on enterprise contracts.
The API is plain REST + JSON, usable with any HTTP client (curl, requests, fetch). Official Python and JavaScript SDKs are on the roadmap.
Per-key default rate limit set per contract. Tiered per-call pricing from $0.25 down to $0.03 by volume. No seat fees.
REST + JSON over HTTPS. SDKs (Python, JavaScript, Go) are on the roadmap; while we publish them, the API is fully usable with any HTTP client. Sign up for a key when you're ready to score.