GetParcelData
US parcel boundaries and assessor data: lookup by APN, point, radius or polygon.
Hosted MCP Server
npx add-mcp 'https://api.getparceldata.com/mcp'Installs into Claude Code, Codex, Cursor and more
Documentation
Find parcels over MCP or REST
Connect an MCP client to https://api.getparceldata.com/mcp, or call the REST API directly. Both cover 161.8M US parcels in 3,164 counties across the 50 states, DC and Puerto Rico, in one schema.
Base URL: https://api.getparceldata.com. Send the key as Authorization: Bearer <key>. The OpenAPI specification describes the parcel lookup endpoints, and llms.txt summarises the product, prices and limits in plain text.
MCP server
The server URL is https://api.getparceldata.com/mcp and the transport is Streamable HTTP. The free tools need no key. For parcel lookups, send your API key in the header Authorization: Bearer <key>. Each lookup costs the same credits as its REST endpoint, and the limits below apply. To try it, get a free key with 100 credits.
check_coverage: Whether a county is covered, or every covered county in a state. Free.get_pricing: API plans, credit costs and extract prices. Free.preview_area: How many parcels a bounding box holds, and which product fits. Free.find_parcels_by_apn: A parcel by APN, county and state. 1 credit.find_parcels_at_point: The parcel at a latitude and longitude. 1 credit.find_parcels_in_radius: Every parcel within a radius of a point. 3 credits.find_parcels_in_polygon: Every parcel intersecting a WKT geometry. 3 credits.
In Claude Code: claude mcp add --transport http getparceldata https://api.getparceldata.com/mcp --header "Authorization: Bearer <key>". Sign-in with OAuth is not available yet, so a client must be able to send the header to use the lookups.
REST without a key
POST /v1/extracts/preview: How many parcels a bounding box holds, and which product fits.GET /v1/extracts/skus: The one-off products on sale and their prices.GET /v1/billing/plans: The API plans, their prices and whether each one is purchasable.
REST with an API key
GET /v1/parcels/apn: A parcel by APN, county and state. 1 credit.GET /v1/parcels/point: The parcel at a latitude and longitude. 1 credit.GET /v1/parcels/radius: Every parcel within a radius of a point. 3 credits.GET /v1/parcels/polygon: Every parcel intersecting a WKT geometry. 3 credits.
Append /geojson to any of these paths for a GeoJSON FeatureCollection at the same cost.
APN lookup
For a property without coordinates, send its APN, county and state to GET /v1/parcels/apn. The response includes GeoJSON boundaries, centroid coordinates and match status.
APNs stay strings, so leading zeros survive. Formatting matches disclose the original identifier. Multiple candidates return an ambiguous status; your application must choose a candidate before attaching a parcel to a property.
APN lookup costs one credit per completed request on every API plan, including no_match and ambiguous results. Your existing API key and spending controls apply.
Limits
- Up to 1,000 parcels per request, or 100 for APN lookups. Page with offset; each page is a new request and is charged again.
- Radius lookups reach up to 5,000 metres from the point.
- Polygon lookups accept a bounding box of up to 25 km². Split a larger area into tiles.
- APN and point requests cost 1 credit. Radius and polygon requests cost 3 credits, however many parcels come back.
- Lookups in counties we do not cover use no credits, and failed requests cost nothing.
- Responses are JSON with WKT geometry, or GeoJSON from the /geojson variant of each endpoint. Coordinates are WGS 84 (EPSG:4326).
Prices
- Starter API plan: $29 a month with 1,000 credits, then $0.029 per credit.
- Growth API plan: $99 a month with 5,000 credits, then $0.020 per credit.
- Scale API plan: $299 a month with 25,000 credits, then $0.012 per credit.
- Custom area download: $49 once. Any area you draw, up to 5,000 parcels. Every field, every format, delivered by email.
- Full county download: $199 once. One entire county, whatever its size — from 82 parcels to 2.4 million. Every field, every format.
Buying ends with a person. POST /v1/extracts/checkout returns a Stripe checkout_url. Give that link to the person you act for, and do not try to complete the payment yourself.