Create a Regrid account at regrid.com; free API access is available for low-volume use, with paid tiers for production workloads
Look up a parcel by address using the typeahead endpoint to resolve a human-readable address to a Regrid ll_uuid (unique parcel identifier)
Fetch the parcel's GeoJSON boundary and attributes by calling the parcel endpoint with the ll_uuid; the response is a GeoJSON Feature Collection
For spatial queries (find all parcels within a polygon or radius), use the /api/v1/parcels endpoint with a geometry parameter in GeoJSON format
Control result size with the limit parameter (default 20, max 1000) and use cursor-based pagination for large geographic queries
Download the OpenAPI specification from your Regrid account portal to generate a typed client or explore endpoints in the API sandbox
Known gotchas
Parcel data is sourced from county records and update frequency varies by county — boundary data in rapidly-developing areas may lag actual subdivision by months
High-volume spatial queries (large radius or polygon sweeps) can return large payloads; set explicit limits and filter to only the fields you need using the fields parameter
For enterprise production use, contact parcels@regrid.com to enable your account for higher throughput; self-serve free tier is rate-limited
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp