Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Locate the target jurisdiction's public parcel FeatureServer (e.g., Colorado's statewide public parcels at gis.colorado.gov/public/rest/services/Address_and_Parcel/Colorado_Public_Parcels/FeatureServer/0, or the county assessor's own ArcGIS Server instance)
Inspect the layer's fields via GET .../FeatureServer/0?f=json to confirm attribute names, since APN/owner/acreage field names vary by jurisdiction
Query by location: GET .../FeatureServer/0/query?geometry=<lon>,<lat>&geometryType=esriGeometryPoint&inSR=4326&outFields=*&f=geojson to retrieve the parcel containing a point
Or query by attribute: GET .../FeatureServer/0/query?where=APN='1234-56-789'&outFields=*&f=geojson to pull a known parcel directly
Import the returned GeoJSON parcel boundary into CAD/GIS software as a reference layer for the retracement survey
Known gotchas
Field names, geometry precision, and update frequency are entirely jurisdiction-specific; there is no single national schema, each county/state service must be inspected individually
Assessor parcel lines are administrative/tax boundaries, not surveyed boundaries — never treat them as a substitute for a retracement survey
Some county services rate-limit or block scripted access without a proper referer/user-agent; check the service's terms of use before automating bulk queries
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?