Legacy API notice
The legacy location, flood and risk endpoints are being retired.
GeoClear is retiring the endpoint families listed on this page. The operational evidence platform, your API key and your account endpoints are not affected.
Current status
No change yet: the listed endpoints answer as before.
Sunset date: to be announced.
What changes, in three steps
- Announcement. Every response from a listed endpoint carries a
Deprecationheader, aSunsetheader with the date above, and aLinkheader that points to this page. Nothing else changes. - Sunset date. Until the date in the
Sunsetheader the endpoints answer exactly as before. - Retirement. After that date the endpoints answer
410 Gonewith a small JSON body that names the sunset date, this page and the replacement documentation.
Endpoint families
| Family | Paths | Status |
|---|---|---|
| Open demo endpoints | /api/demo/api/demo/suggest/api/demo/cong-district/api/demo/bulk/api/demo/reverse/api/demo/risk/api/demo/enrich | Answering; sunset above |
| Key-gated risk score and outcome feedback | /v1/risk/v1/outcomes | Answering; sunset above |
| Address lookup, geographic utilities, enrichment, proximity | /api/address/api/address/bulk/api/address/csv/api/suggest/api/zip/{zip}/api/state/{code}/api/states/api/county/api/city/api/neighborhood/api/zips/api/near/api/stats/api/coverage/api/enrich/v2/proximity | Retired since 2026-07-10 |
| MCP address tool server | /mcp | Retired since 2026-07-10 |
What to do
If your integration calls one of the listed endpoints, write to support@geoclear.io before the sunset date and we will work out the path with you. The current platform is described in the documentation.