API access
Your AI client reaches US Soils 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 soil survey areas represented in SSURGO or STATSGO. A request past that edge comes back empty rather than approximated.
- ⚠ Which years it spans, because the covered period is not declared.
- ⚠ Anything USDA NRCS Soil Data Access does not publish. ParcelOps returns this source as it stands and never fills a blank field from a different one.
- ⚠ Soil survey context does not replace current field investigation, engineering, or site-specific geotechnical analysis.
Methods (3)
A method is one call your agent can make against this source.
queryAtPoint
readQuery soil map units at a point using the shared point-query method name.
What you must providelatitudelongitudeRecords returnedsoil-map-unitHow to get more resultsnoneCoordinate systemEPSG:4326FreshnessScheduled (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 }Output schema
{ "type": "object", "properties": { "latitude": { "type": "number", "minimum": -90, "maximum": 90 }, "longitude": { "type": "number", "minimum": -180, "maximum": 180 }, "source": { "type": "string" }, "coverage": { "type": "string" }, "mapUnits": { "type": "array", "items": { "type": "object", "additionalProperties": true } }, "notice": { "type": "string" } }, "required": [ "latitude", "longitude", "source", "mapUnits", "notice" ], "additionalProperties": true }querySoilAtPoint
readBackward-compatible alias for queryAtPoint.
What you must providelatitudelongitudeRecords returnedsoil-map-unitHow to get more resultsnoneCoordinate systemEPSG:4326FreshnessScheduled (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 }Output schema
{ "type": "object", "properties": { "latitude": { "type": "number", "minimum": -90, "maximum": 90 }, "longitude": { "type": "number", "minimum": -180, "maximum": 180 }, "source": { "type": "string" }, "coverage": { "type": "string" }, "mapUnits": { "type": "array", "items": { "type": "object", "additionalProperties": true } }, "notice": { "type": "string" } }, "required": [ "latitude", "longitude", "source", "mapUnits", "notice" ], "additionalProperties": true }getServiceInfo
readReturn USDA source metadata and caveats.
FreshnessScheduled (source-level)Input schema
{ "type": "object", "properties": {}, "required": [], "additionalProperties": false }
Where this source is used
- Texas grid and land screening
Put Texas grid context next to the state parcel record and the site constraints in one screening call.
- 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.
- Are there wetlands on this property?
- What are the soils under this site?
