API access
Your AI client reaches USGS Elevation 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, Alaska, Hawaii, and U.S. territories where National Map elevation data are published. A request past that edge comes back empty rather than approximated.
- ⚠ Which years it spans, because the covered period is not declared.
- ⚠ How current a field is, because the refresh schedule is not declared.
- ⚠ Anything USGS National Map Elevation Point Query Service (3DEP) does not publish. ParcelOps returns this source as it stands and never fills a blank field from a different one.
- ⚠ Returned elevations are interpolated from elevation models and are not a surveyed elevation.
Methods (2)
A method is one call your agent can make against this source.
getElevation
readGet elevation at a WGS84 point.
What you must providelatitudelongitudeRecords returnedelevationHow to get more resultsnoneCoordinate systemEPSG:4326Input schema
{ "type": "object", "properties": { "latitude": { "type": "number", "minimum": -90, "maximum": 90 }, "longitude": { "type": "number", "minimum": -180, "maximum": 180 }, "units": { "type": "string", "enum": [ "Meters", "Feet" ] } }, "required": [ "latitude", "longitude" ], "additionalProperties": false }Output schema
{ "type": "object", "properties": { "kind": { "const": "parcelops.public-data" }, "schemaVersion": { "const": "1.0" }, "dataset": { "type": "object", "required": [ "connector", "method", "name", "jurisdiction" ], "additionalProperties": true }, "query": { "type": "object", "additionalProperties": true }, "summary": { "type": "object", "properties": { "matchedRecords": { "type": [ "integer", "null" ], "minimum": 0 }, "returnedRecords": { "type": "integer", "minimum": 0 }, "truncated": { "type": "boolean" } }, "required": [ "matchedRecords", "returnedRecords", "truncated" ], "additionalProperties": true }, "records": { "type": "array", "items": { "type": "object", "additionalProperties": true } }, "pagination": { "type": [ "object", "null" ], "additionalProperties": true }, "source": { "type": "object", "required": [ "name", "url", "retrievedAt" ], "additionalProperties": true }, "export": { "type": "object", "required": [ "tool", "connector", "method", "args", "recordPath", "formats", "columns", "suggestedFilename", "maximumRows" ], "additionalProperties": true }, "privacy": { "type": "object", "required": [ "classification", "excludedFields" ], "additionalProperties": true }, "caveats": { "type": "array", "items": { "type": "string" } } }, "required": [ "kind", "schemaVersion", "dataset", "query", "summary", "records", "pagination", "source", "export", "privacy", "caveats" ], "additionalProperties": true }getServiceInfo
readReturn USGS source metadata and caveats.
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.
- What are the soils under this site?
- What is the elevation of this property?
- Will a tall structure here need FAA review?
