Address resolution
Census Geocoding Services resolves the submitted U.S. address to a matched address, coordinates and geographic context.
The human interface and the agent interface are built around the same normalized address profile and the same source boundaries. UtilityDataUSA does not create a separate “AI truth” disconnected from the underlying public evidence.
The core flow resolves the address through Census, adds county/state geography, then runs source adapters and public-context layers before returning one structured profile for both the website and agent tools.
Census Geocoding Services resolves the submitted U.S. address to a matched address, coordinates and geographic context.
FEMA, EPA, USGS, EIA context, PHMSA public context and state-aware 811 guidance are handled with their own source boundaries.
Each source keeps its own status, evidence, source role and limitation instead of being flattened into one unsupported conclusion.
The remote MCP endpoint exposes 11 read-only source tools over stateless Streamable HTTP. Supported protocol versions: 2025-11-25, 2025-06-18 and 2025-03-26. Browser WebMCP exposes 14 tools, including the separately limited AI action.
These public endpoints have request limits and no service-level guarantee. Check every source status. The MCP endpoint does not call paid AI, create tickets or write private records.
Human-friendly names are shown first. The exact tool IDs remain visible for developers and agent integrations.
get_weather_contextNWS forecasts and independently checked alerts.
get_elevation_contextUSGS 3DEP elevation, resolution and source acquisition date.
get_soil_contextUSDA map-unit components and recorded drainage/hydrologic properties.
get_utilitydatausa_contextReturns the product context, source boundaries and important safety limitations.
find_us_addressResolves a submitted U.S. address through the same Census address workflow used by the site.
get_address_profileReturns the normalized profile across all currently connected and public-context sources.
interpret_address_profileInterprets only the structured evidence returned by the address profile and preserves source limitations.
get_flood_contextReturns FEMA flood-hazard context for the matched address location when available.
get_environment_screeningReturns EPA facility-screening context around the matched address.
get_water_contextReturns nearby USGS hydrologic monitoring context around the matched address.
get_electric_utility_contextReturns Census county/state geography plus EIA context without claiming an address-level utility owner.
get_pipeline_contextReturns PHMSA NPMS public pipeline/operator context and official follow-up links, never exact line locating.
get_811_guidanceReturns state-aware excavation-safety follow-up without replacing the required one-call process.
list_authoritative_sourcesLists current source roles and keeps live, public-context, follow-up and expanding states explicit.
An unavailable public endpoint must not silently become a “no issue found” result. The normalized profile keeps explicit source states so downstream software can reason about missing evidence correctly.
Authentication, usage units, credits and commercial API plans will be designed after the consumer workflow and source coverage are in the right shape. The current priority is a clear, useful product with trustworthy source handling.