Independent public-data platform using U.S. government and utility sourcesHow source transparency works
API & Developers

One address layer for people, software and agents.

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.

Architecture

From one address to normalized 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.

1

Address resolution

Census Geocoding Services resolves the submitted U.S. address to a matched address, coordinates and geographic context.

2

Source adapters

FEMA, EPA, USGS, EIA context, PHMSA public context and state-aware 811 guidance are handled with their own source boundaries.

3

Normalized profile

Each source keeps its own status, evidence, source role and limitation instead of being flattened into one unsupported conclusion.

U.S. address · Census match · geography · source adapters · public context · normalized evidence · human UI + WebMCP tools
Connect your software

Public API and remote MCP.

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.

MCP endpoint: /api/mcp
Address profile: GET /api/webmcp/address-profile?q=YOUR_ADDRESS

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.

Current WebMCP tools

Read-only, source-aware tools.

Human-friendly names are shown first. The exact tool IDs remain visible for developers and agent integrations.

Weather & Alerts

get_weather_context

NWS forecasts and independently checked alerts.

Terrain Elevation

get_elevation_context

USGS 3DEP elevation, resolution and source acquisition date.

Soil Survey

get_soil_context

USDA map-unit components and recorded drainage/hydrologic properties.

UtilityDataUSA Context

get_utilitydatausa_context

Returns the product context, source boundaries and important safety limitations.

Find U.S. Address

find_us_address

Resolves a submitted U.S. address through the same Census address workflow used by the site.

Address Profile

get_address_profile

Returns the normalized profile across all currently connected and public-context sources.

AI Interpretation

interpret_address_profile

Interprets only the structured evidence returned by the address profile and preserves source limitations.

Flood Context

get_flood_context

Returns FEMA flood-hazard context for the matched address location when available.

Environment Screening

get_environment_screening

Returns EPA facility-screening context around the matched address.

Water Context

get_water_context

Returns nearby USGS hydrologic monitoring context around the matched address.

Electric Utility Context

get_electric_utility_context

Returns Census county/state geography plus EIA context without claiming an address-level utility owner.

Pipeline Context

get_pipeline_context

Returns PHMSA NPMS public pipeline/operator context and official follow-up links, never exact line locating.

811 Guidance

get_811_guidance

Returns state-aware excavation-safety follow-up without replacing the required one-call process.

Authoritative Sources

list_authoritative_sources

Lists current source roles and keeps live, public-context, follow-up and expanding states explicit.

Coming later

Paid API access comes after the product flow.

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.