API access
Your AI client reaches US Census Address & Geography through one ParcelOps MCP endpoint, so there is no separate key to hold for it and no per-source client to write. Reaching it takes no credentials of your own.
Where it came from
Freshness and coverage
What this source cannot tell you
- ⚠ Anything outside United States and Puerto Rico. A request past that edge comes back empty rather than approximated.
- ⚠ Which years it spans, because the covered period is not declared.
- ⚠ Anything US Census Bureau Geocoding Services does not publish. ParcelOps returns this source as it stands and never fills a blank field from a different one.
- ⚠ A matched address or Census geography is not a parcel, title, boundary, or ownership record.
Methods (5)
A method is one call your agent can make against this source.
geocodeAddress
readMatch one US address and return its coordinate and Census match.
What you must provideaddressFreshnessScheduled (source-level)Input schema
{ "type": "object", "properties": { "address": { "type": "string", "minLength": 3, "maxLength": 300 } }, "required": [ "address" ], "additionalProperties": false }geocodeAddressComponents
readMatch structured US address fields.
What you must providestreetFreshnessScheduled (source-level)Input schema
{ "type": "object", "properties": { "street": { "type": "string", "minLength": 1, "maxLength": 200 }, "city": { "type": "string", "maxLength": 120 }, "state": { "type": "string", "maxLength": 40 }, "zip": { "type": "string", "pattern": "^\\d{5}(?:-\\d{4})?$" } }, "required": [ "street" ], "additionalProperties": false }reverseGeocode
readResolve a US coordinate to Census geographies and FIPS codes. No address.
What you must providelatitudelongitudeFreshnessScheduled (source-level)Input schema
{ "type": "object", "properties": { "latitude": { "type": "number", "minimum": -90, "maximum": 90 }, "longitude": { "type": "number", "minimum": -180, "maximum": 180 } }, "required": [ "latitude", "longitude" ], "additionalProperties": false }getGeography
readReturn Census geography layers and FIPS codes for a US coordinate.
What you must providelatitudelongitudeFreshnessScheduled (source-level)Input schema
{ "type": "object", "properties": { "latitude": { "type": "number", "minimum": -90, "maximum": 90 }, "longitude": { "type": "number", "minimum": -180, "maximum": 180 } }, "required": [ "latitude", "longitude" ], "additionalProperties": false }Accepts latitude and longitude from a geocode result, never address text.
getServiceInfo
readReturn source, coverage, and legal-use notes.
FreshnessScheduled (source-level)Input schema
{ "type": "object", "properties": {}, "required": [], "additionalProperties": false }
Where this source is used
- Housing program eligibility checks
Check tax credit designations, rural program maps, and existing affordable inventory for an address from your own code.
- Land research
Parcel records, ground conditions, and what reaches the property line, for raw and rural land.
- Data center siting
Power, water, transport, airspace, and hazard screening for a site before anyone signs anything.
- Commercial real estate
Parcel and assessment records, building programs, and the entity on the other side of the deal.
- Residential real estate
The parcel record, the housing programs that touch an address, and the conditions a buyer asks about.
- Real estate law
Federal rule text, rulemaking dockets, party records, and the property facts a filing has to state.
- Realtors and brokerages
The facts behind a listing, the programs a buyer may qualify for, and your own files in the same place.
- What census tract is this address in?
