Self-serve API access from $79· Custom enterprise contracts · Founder-led integration
PropData is the property intelligence layer enterprise products should not have to assemble source by source or country by country. The U.S. product starts with 166M+ indexed parcel records across all 50 states, while the broader PropData network now spans 400M+ property and parcel records and 7B+ normalized data points across seven country-native products.
Use one PropData account across production applications, supported AI clients, developer tools, bulk delivery, and custom contracts. The same governed data layer stays underneath every surface.
Compatibility labels identify supported delivery surfaces. No platform endorsement or affiliation is implied.
Property products lose time and margin when engineering teams have to reconcile county records, parcel geometry, market feeds, risk layers, and vendor-specific schemas before they can ship the feature customers asked for. PropData turns that fragmented work into one programmable intelligence layer.
Give product teams normalized property intelligence through a stable integration so engineering can spend its time on underwriting, mapping, verification, automation, and customer experience.
Resolve identity, geometry, records, valuation, market context, comps, rent, and risk through one relationship—with custom routes and response shapes when your system needs them.
Carry official-source context, canonical identifiers, coverage status, and geometry behavior into the response so teams can understand what is known, what is missing, and what should happen next.
ProductEngineeringOperationsAI teams
We will map the inputs, response contract, priority markets, and delivery path around the product your customers actually use.
Run distinct schemas, inspect provenance, connect an AI client, and see pricing before a sales call. PropData is positioned as infrastructure builders can evaluate directly—not a dashboard promise.
Endpoint-aware inputs with readable JSON and parsed responses on the homepage.
Use the same PropData account in Cursor, ChatGPT, Claude, REST, and other MCP clients.
Property, geometry, comps, market, rent, risk, usage, changelog, and custom contracts.
Published monthly limits and upfront pricing—no contact-sales gate for base access.
Choose monthly or annual U.S. API access below and continue directly to secure Stripe checkout. Every plan includes production REST access, the customer-safe OAuth MCP connector, and the interactive workspace. Country-local self-serve pricing for Great Britain, New Zealand, Australia, Estonia, France and Spain is available through PropData Global.
enrich=fullPropData is no longer limited to code calling an endpoint. Developers can use the same production account inside Cursor. Teams can connect compatible ChatGPT, Claude, and MCP clients. Applications can keep using REST, bulk, and custom contracts. The intelligence, account controls, and usage plan stay unified underneath.
Let Cursor resolve properties, compare markets, inspect comps, estimate rent, and use neighborhood intelligence while it writes your application.
ADD PROPDATA TO CURSOR →Use customer-safe tools instead of pasting raw API responses or asking an assistant to infer property facts from unstructured pages.
VIEW CONNECTION GUIDE →Expose narrowly defined lookup, market, comp, rent, and neighborhood functions with explicit coverage and match status.
VIEW MCP DOCUMENTATION →Call the API directly, run bulk workflows, request custom response contracts, or embed PropData invisibly beneath your own interface.
EXPLORE ENDPOINTS →{
"mcpServers": {
"propdata": {
"url": "https://propdata-mcp.sales-fd3.workers.dev/mcp"
}
}
}
The public connector exposes customer-safe property and market tools. It does not expose PropData’s internal county imports, canonical files, checkpoints, infrastructure credentials, deployment controls, or private QA systems.
The full PropData API Reference & Integration Guide documents authentication, property and market routes, coordinate-to-parcel resolution, parcel geometry, ?enrich=full, comps, rent, neighborhood and risk context, MCP workflows, usage, errors, and implementation examples.
PropData is backed by a live real estate operating system that discovers official public infrastructure, validates jurisdiction and schema fit, publishes trusted intelligence, monitors customer-priority coverage lanes, and revisits known data to detect change.
We do not freeze operating metrics into this homepage. Open the live OS to see current aggregate production, geography, publishing, refresh, field-classification, quality, and priority-lane activity.
Select a verified parcel from Florida, Michigan, New York, Minnesota, Nevada, or North Carolina. Every option preserves its real county identifier and official polygon—no generic pins, placeholder IDs, or fabricated nationwide examples.
PropData is not another property-search dashboard. It is a programmable property and geospatial intelligence layer designed to sit underneath real estate, mapping, appraisal, insurance, solar, roofing, construction, field-service, site-selection, and AI products.
Explore production endpoints →Address, official parcel ID, or latitude and longitude. PropData resolves the county, canonical parcel identifier, and matching property record.
GET /v1/property/by-location?lat=&lng=
Use GeoJSON boundaries, centroids, and bounding boxes for click-a-parcel selection, overlays, acreage analysis, site planning, and spatial intersections.
GET /v1/parcel-geometry
Attach ownership, valuation, taxes, sales, characteristics, comps, rent, flood, hazard, neighborhood, affordability, risk, and national EPA facility-proximity context.
?enrich=full
REST endpoints, MCP connectors, bulk workflows, delta feeds, white-label infrastructure, custom endpoints, and custom response shapes.
REST + MCP + BULK + CUSTOM
ENRICH=FULLPropData now resolves the block-level people, housing, and economic context around a property, then pairs it with the tract-level incentive contract investors actually need.
AI builders, underwriting teams, and institutional investors can move from parcel truth to community truth in the same response. No ZIP-code approximation. No second demographic vendor. No separate Opportunity Zone join.
"request_id": "req_01J8PD7F31",
"enrichment": "full",
"property": { "id": "pd_demo_7f31", "match_level": "parcel" },
"tract_intelligence": {
"geoid": "27053104500",
"geography": "census_tract",
"opportunity_zone": {
"designated": true,
"designation_vintage": "2018",
"statutory_basis": "IRC_1400Z"
},
"median_household_income": 54820,
"poverty_rate": 0.184,
"source": "US_CENSUS_TRACT_QOZ"
}"block_group_intelligence": {
"geoid": "270531045001",
"geography": "block_group",
"population": 1462,
"households": 812,
"median_household_income": 61740,
"renter_occupied_pct": 0.684,
"vacancy_rate": 0.071,
"median_gross_rent": 1328,
"low_response_score": 23.6,
"source": "US_CENSUS_2026_PDB"
}"provenance": { "geography_vintage": "2020", "pdb_vintage": "2026", "coverage": "matched" }
}
Give models normalized community features at the exact geography they describe, not a broad ZIP-code proxy.
Carry tract-level Qualified Opportunity Zone status beside the parcel and its immediate block-group profile.
Move from a national property universe to a block-aware acquisition, site-selection, or portfolio decision.
ENRICH=FULLPropData now adds national EPA Facility Registry Service proximity intelligence to the same property response your application already uses.
Start from a verified parcel centroid, search the indexed federal snapshot by radius, rank nearby records by distance, and preserve source-program context for underwriting, site selection, lending, appraisal, and portfolio screening.
/v1/property?county_fips=36061&parcel=1008350041&enrich=full
Coverage status, verified-coordinate lineage, distance-ranked matches, source release, program associations, and explicit limitations travel with the enrichment.
Screening limitation: EPA FRS proximity is not proof of contamination, liability, or current regulatory status. A negative result covers only coordinate-bearing records in the indexed 2026-08-01 snapshot within the requested radius; 1,114,455 source records without coordinates cannot support a favorable universal negative.
PropData keeps the 166M+ U.S. parcel foundation at the core and extends the same source-aware infrastructure model internationally. Great Britain, New Zealand, Australia, and Estonia are the first live expansion markets—not the finish line. Scale and Enterprise customers can build across the current footprint while PropData continues adding countries based on source quality, licensing, and customer demand.
PropData now connects the U.S., Great Britain, New Zealand, Australia, and Estonia through the same API-first operating model—while preserving source-native identity, provenance, and country-specific truth.
All 50 states with address, parcel-ID and coordinate resolution, county-sourced assessor and GIS data, market intelligence, geometry, valuation, risk, and enrichment where published and verified.
50-STATE FOUNDATIONOrdnance Survey OpenUPRN provides the national addressable-property identity spine across England, Scotland, and Wales, designed to link into official identifiers, geometry, title, and transaction layers.
ORDNANCE SURVEYToitu Te Whenua LINZ parcels, addresses, property titles, and title-to-parcel associations establish a national source-native identity and geospatial layer for New Zealand workflows.
TOITU TE WHENUA LINZAustralia is modeled through its source-native state and territory land systems, normalized into the same country-neutral identity, geometry, and provenance layer without flattening local identifiers.
STATE + TERRITORY SOURCESOfficial national cadastral parcels and the ADS address/object graph preserve cadastral IDs, ADR_ID, ADS_OID, ADOB_ID, geometry, lifecycle, and provenance inside the same country-aware PropData contract.
ESTONIAN LAND AND SPATIAL DEVELOPMENT BOARD · ADS + CADASTRALPropData is building reusable national ingestion, identity, provenance, and geospatial infrastructure so each new country strengthens the same platform instead of creating another silo. Customer demand, licensing, and official-source quality help determine what comes next.
Country-specific fields, identifiers, licensing, geometry, and enrichment depth vary by official source. PropData preserves source-native identifiers and explicit availability rather than manufacturing fields that a jurisdiction does not publish.
PropData is the independent data infrastructure beneath serious real-estate products. Resolve any property from an address, parcel ID, or coordinates—then add ownership, valuation, tax, sales, geometry, comps, rent, market, neighborhood, hazard, EPA facility proximity, and investment intelligence through one platform.
Replace fragmented vendors and brittle joins with one production layer built for property search, underwriting, mapping, automation, and AI.
The parcel index is a major part of the value and should be visible. It is not, however, a blanket claim that every county publishes the same fields or that every parcel has verified geometry. PropData separates each layer so developers can understand exactly what is available for their workflow.
Rent benchmarks, listing velocity, inventory, affordability, demographics, appreciation, mortgage context, hazards, and market signals.
NATIONWIDE LAYERThe national foundation for addresses, official parcel identifiers, county routing, ownership, values, tax and sale fields where the official source publishes them.
50-STATE FOUNDATIONExact-ID crosswalks, source-schema validation, row reconciliation, null preservation, duplicate checks, and repeated property-to-enrichment gates.
County routing, point-in-polygon matching, GeoJSON boundaries, centroids, bounding boxes, and spatial workflows expanding through verified markets daily.
County data is fragmented by jurisdiction, schema, identifier format, and GIS design. PropData routes each market through an official-source workflow and publishes verified coverage only after the full location-to-parcel-to-enrichment chain holds up in production.
null. A legitimate zero remains zero. Provenance, source identifiers, retrieval context, and deliberately empty fields can travel with the record.
Assessor, tax, public-record, and GIS systems are identified and validated at the county level.
Leading zeros, punctuation, alternate parcel IDs, and assessor-to-GIS crosswalks are preserved and tested.
Latitude and longitude are routed to the correct county and matched to parcel boundaries with point-in-polygon logic where configured.
Row totals, duplicates, geometry, null behavior, source fields, and geographic canaries are audited before release.
Address, parcel-only, coordinate, geometry, and full-enrichment workflows are tested repeatedly. Uncertainty is quarantined, not guessed.
Most static databases treat a miss as the end of the request. PropData treats it as structured coverage intelligence. We preserve the safe API response while turning repeated county, workflow, and field-level gaps into an evidence-backed expansion queue.
When a source does not support a field or a county workflow has not cleared production gates, the API returns a truthful status, source context, and nulls—not invented values.
coverage_status: "not_configured"
annual_tax: null
source_provenance: preserved
The unsupported county, missing route, failed crosswalk, geometry gap, or incomplete enrichment chain becomes a structured work item that can be ranked against real customer demand.
county + endpoint + failure stage
→ source investigation
→ verified production coverage
Address, parcel ID, coordinates, geometry, assessor join, or enrichment.
Builder+ requests and repeated production gaps inform the active queue.
Assessor, tax, public record, GIS, and exact source schemas.
Leading zeros, punctuation, alternate IDs, geometry links, and null behavior.
Row reconciliation, duplicates, canaries, point-in-polygon, and repeated chains.
The repaired route improves every future customer using that market.
Need coordinate resolution, geometry, assessor enrichment, or a custom field set in a specific county? Builder, Scale, and Enterprise customers can submit priority markets. Approved requests are reviewed against source availability and moved into the active engineering and QA queue.
A national real-estate platform needed a dependable coordinate → parcel → assessor → full-enrichment chain across a multi-state, dozens-of-counties rollout. That requirement drove county-specific routing, exact-ID crosswalks, geometry resolution, live canaries, repeated production gates, and a much stronger product for every future mapping customer.
PropData combines a 166M+ record U.S. parcel index across 50 states with direct county assessor and GIS records, the official 2026 Census Planning Database at block-group resolution, tract-level Qualified Opportunity Zone intelligence, national EPA Facility Registry Service proximity, market, rent, economic, flood, hazard, safety, and proprietary layers. The national parcel foundation matters, but the larger value is resolving a location to the correct parcel and attaching the exact property, community, incentive, environmental-screening, and risk context your application needs without stitching together separate providers.
The government's official rent benchmark — the same data used to set Section 8 voucher amounts. Every county in America. Studio through 4-bedroom. Ground truth for affordability analysis.
ZORI — Zillow's smoothed median asking rent for all homes and multifamily. The most cited rent trend dataset in real estate. ZIP, metro, state, and national with 10 years of history.
Monthly listing data: median prices, days on market, active inventory, new listings, price reductions, price per sqft. The pulse of the for-sale market at ZIP level.
Sale-to-list ratio, % sold above list, days to pending, months of supply. The sharpest demand signal in public real estate data.
Vacancy rates, renter %, median income, rent-to-income ratio, poverty rate, unemployment. Affordability context nobody else includes at this price point.
Mortgage rates, shelter inflation, national vacancy rate, and housing starts. National economic context alongside local market data.
Quarterly home price appreciation by state and metro. The definitive government measure of home value change — used by mortgage lenders, Fed economists, and institutional investors.
Monthly new construction by unit type. The forward-looking supply signal — permits today become inventory in 12-18 months. Predicts rent pressure before it shows up in listing data.
Weighted rent estimate model built on owned data. ZORI (40%) + Census ACS (25%) + HUD FMR (20%) + Redfin cap rate (15%). Returns low/mid/high range with confidence score. No third-party dependency.
Direct-ingest property and parcel records from official county assessor, tax, public-record, and GIS systems. Ownership, situs and mailing addresses, valuation, taxes, sales, characteristics, official identifiers, and parcel geometry where configured. Coverage is verified county by county and expands continuously.
Comparable sales engine built on our 166M+ parcel database. Ranked comps scored on price, sqft, recency, and bedroom count. Low/mid/high range + avg price per sqft. Delivered through the same API workflow.
Resolve addresses, coordinates, ZIP codes, county FIPS, and official parcel identifiers through one routing layer. Coordinate workflows can match a map point to the underlying parcel and continue directly into geometry and enrichment.
18 natural hazard risk scores by county — wildfire, flood, hurricane, tornado, earthquake, hail, heat wave, drought, winter weather, and 9 more. Per-capita annualized loss rate percentiles so you're not comparing Maricopa County to rural Kansas unfairly. The same dataset FEMA uses to allocate disaster preparedness funds. Visualized on a live US heat map. Now inside your API call.
Composite A–F grade combining school quality (100K+ schools), poverty, unemployment, social vulnerability, resilience, and crime. A combined due-diligence layer for software and underwriting workflows.
Official Census Tract identifiers paired with Qualified Opportunity Zone designation and eligibility context. The tract remains the stable macro contract for statutory incentives, portfolio screening, underwriting, and compliance workflows.
The high-resolution community layer: selected housing, demographic, socioeconomic, and operational measures across 242,336 official block groups. PropData normalizes that source universe into block_group_intelligence for full property enrichment.
FEMA National Flood Hazard Layer flood zone per property — Zone A, AE, X — mandatory insurance baked in. Skip trace returns owner phones, email, and equity data. Microsoft ML building footprints add sqft and height per structure.
National environmental-facility screening from 5,300,149 federal source rows, including 4,185,694 coordinate-bearing records indexed for verified parcel-centroid proximity searches. Returns coverage, distance-ranked matches, release provenance, and program associations such as ACRES, SEMS, RCRAInfo, and TRI through enrich=full.
PropData separates source ingestion, county routing, canonical storage, verification, caching, authentication, and API delivery into dedicated infrastructure layers. Official county records and supporting market sources refresh on source-appropriate schedules, while validated responses are delivered through the Cloudflare edge.
PropData runs on 10+ dedicated Workers inside PropTechUSA.ai's 200+ Worker production stack — the same infrastructure powering IntelligentHomeBuying, IntelligentLandlord, and LHBUSA. No monolith. Pure edge.
All market data cached at Cloudflare's edge. 7-day TTL. Sub-50ms reads globally.
15+ normalized tables. ZORI, Realtor, Redfin, HUD FMR, Census ACS + 2026 PDB, FHFA HPI — ZIP, state, and metro tiers. Indexed for fast queries.
Tiered access: Starter 50 req/hr, Builder 500 req/hr, Internal unlimited. Keys provisioned in KV instantly on signup.
The dashboard demonstrates the response. Production teams integrate the API and select only the layers their workflow needs.
GET /v1/property?parcel=...&enrich=full
Return the core record, then attach tax, equity context, comps, rent, flood, hazards, neighborhood, affordability, risk flags, and investment scoring.
The homepage shows the product and its most important workflows. The full reference, authentication, schemas, coverage behavior, error handling, and examples live in the dedicated documentation and downloadable API guide.
# 1 · Coordinates → exact parcel + official boundary curl -sS \ "https://propdata-api-worker.sales-fd3.workers.dev/v1/property/by-location?lat=25.7689792&lng=-80.1903649&include_geometry=1" \ -H "x-api-key: pd_live_YOUR_KEY" # 2 · Exact parcel ID → full enrichment curl -sS \ "https://propdata-api-worker.sales-fd3.workers.dev/v1/property?county_fips=12086&parcel=0102100001060&enrich=full" \ -H "x-api-key: pd_live_YOUR_KEY" # 3 · ZIP → market + rent intelligence curl -sS \ "https://propdata-api-worker.sales-fd3.workers.dev/v1/market?zip=33131" \ -H "x-api-key: pd_live_YOUR_KEY"
/v1/propertyAddress or parcel lookup/v1/property/by-locationCoordinates to parcel/v1/parcel-geometryGeoJSON boundary?enrich=fullOne-call due diligence/v1/market · /rent · /estimateMarket, rent, and AVM/v1/comps · /neighborhoodComparable + location context/v1/property/deltaChanged-record delivery/v1/usage · /health · /changelogOperations + visibilitypropdata-mcpCursor, ChatGPT, Claude + MCPUse only the endpoints you need, or combine them into a single property-intelligence workflow. PropData is designed to replace fragmented data plumbing, not merely add another dashboard to your stack.
/v1/property
/v1/geocode
/v1/property/by-location
/v1/parcel-geometry
/v1/property
?enrich=full
/v1/market
/v1/rent
/v1/estimate
/v1/neighborhood
/v1/zip-intel
/v1/state-intel
/v1/property/delta
/v1/preforeclosure/delta
/v1/changelog
REST + MCP + CUSTOM
Use it to inspect responses, manage keys, monitor usage, and test workflows. Customer-facing products should call the PropData API directly.
Buy an AVM from one vendor, parcel geometry from another, permits from a third, mortgage records from an incumbent, environmental context somewhere else, and an AI connector on top. You still own the joins, licensing, schemas, coverage gaps, evidence chain, and every failure between them.
Property + parcel identities
Live national footprints
Fields returned where supported
MCP · bulk · custom delivery
PropData resolves identity first, then attaches geometry, assessor, ownership, valuation, mortgage, permit, recorder-document, market, community, environmental, and provenance intelligence to the same property contract. The architecture now spans four national footprints and every modern delivery surface.
Every connected source strengthens the same underlying property identity instead of creating another disconnected dataset your customer has to reconcile.
IDENTITY BEFORE ENRICHMENT
Address, official parcel identifier, coordinates, geometry, source, match status, and coverage status establish what the property is before additional facts attach.
DEEP U.S. PROPERTY CONTEXT
Assessor fields, ownership, valuation, tax, sales, comps, rent, markets, hazards, Community Intelligence, EPA proximity, and provenance can resolve through one workflow.
MORTGAGE + DOCUMENT INTELLIGENCE
Recorder events, lender and borrower entities, confidence-aware property matching, and official document files can remain connected to the canonical parcel where available.
PERMITS + PUBLIC RECORDS
Permit histories and expanding public-record layers create decision inputs for underwriting, renovation intelligence, risk, acquisitions, and monitoring products.
AI-NATIVE DELIVERY
The same governed intelligence can move through production REST, OAuth-protected MCP, bulk delivery, webhooks, white-label systems, and custom response contracts.
DEMAND-LED COMPOUNDING
The ingestion pipeline is already built. Qualified customer needs can prioritize new counties, sources, fields, documents, countries, and purpose-built endpoints.
Property · geometry · ownership · valuation · mortgages · official documents · permits · comps · rent · market · Community Intelligence · EPA FRS · provenance.
PropData is extending deeper into pre-foreclosure, tax liens, code violations, permit coverage, mortgage history, divorce indicators, recorder events, and additional international markets—all on the same country-neutral property architecture.
| Buyer test | PropData | RentCast | ATTOM | Regrid | BatchData | Mashvisor | Cotality |
|---|---|---|---|---|---|---|---|
| What the buyer actually gets | ONE SYSTEM · global identity + deep enrichment | U.S. property + AVM API | U.S. enterprise data catalog | Parcel + spatial system | Property + contact workflows | Rental investment analytics | Institutional product ecosystem |
| Live published footprint | 400M+ · U.S. + GB + NZ + AU + EE | 150M+ U.S. properties | U.S.-centered property datasets | 160M+ U.S. · 11M+ Canada · global parcels | U.S. property workflows | U.S. housing + rental data | Multi-country enterprise footprint |
| Canonical identity resolution | Address + parcel ID + coordinates → one property | Address + property search | Address + APN + geo products | Coordinate/polygon → parcel | Address + geocode + property lookup | Address + location analytics | CLIP identity + spatial products |
| Depth from one verified property | 100+ official fields in one property response | Property + AVM + listing fields | Deep fields across a broad product catalog | Parcel + land + ownership attributes | Property + contact signals | Rental ROI + neighborhood fields | 200+ fields across an enterprise ecosystem |
| Evidence behind the field | Provenance + mortgage events + official documents | County-derived record fields | Recorder + loan datasets | Parcel source metadata | Property + permit results | Property + listing context | Verified sources + CLIP linkage |
| Permits + expanding public records | Attached to the same property contract | Property-record focus | Permit + foreclosure products | Matched parcel datasets | Permit details + monitoring | Property/tax/listing context | Broad public-record ecosystem |
| Intelligence without more joins | Comps + rent + market + community + EPA + risk | Comps + rent + market | Broad intelligence across products | Zoning + spatial add-ons | Acquisition-oriented signals | Rental ROI + neighborhood analytics | Analytics + climate products |
| AI + production delivery | REST + OAuth MCP + bulk + custom contracts | REST + MCP + Zapier | REST + MCP + bulk/cloud | REST + MCP + tiles + bulk | REST + MCP + async jobs | REST + tailored APIs | REST + MCP + cloud + AI agents |
| When the required field is missing | Direct source engineering can expand the graph | Consume the published API catalog | Enterprise product engagement | Add a dataset or matched layer | Use available workflow products | Use available analytics products | Enterprise product engagement |
| What remains for a global, evidence-rich product | SUPPORTED COVERAGE · ONE CONTRACT · ONE GRAPH | Add geometry, evidence, public records + global identity | Package products + complete enterprise implementation | Add property depth, markets, evidence + public records | Add global identity, geometry + broader intelligence | Add canonical parcels, evidence + public records | Complete enterprise procurement + product integration |
Among the public products reviewed, PropData uniquely combines four-country property identity, deep U.S. enrichment, evidence-linked records, integrated intelligence, and customer-directed source engineering through one independent platform.
Bring your required fields, markets, volumes, and delivery contract. We will show what PropData can consolidate, where a specialist may still make sense, and what the next enrichment layer should be.
Custom endpoints are a core PropData capability—not a footnote. Qualified integrations can combine multiple source layers, rename fields, normalize property-type dictionaries, remove unnecessary payload weight, add customer-specific logic, or expose an exact response contract that drops into an existing product.
CUSTOM ROUTESCombine coordinate resolution, parcel geometry, assessor fields, comps, flood, rent, and risk into one purpose-built request.
RESPONSE SHAPESRename fields, flatten nested objects, map property types to ATTOM or internal dictionaries, and return only the fields your product consumes.
PRIORITY COVERAGEOfficial-source discovery, county routing, canonical IDs, imports, geometry, reconciliation, and live QA can follow a qualified customer roadmap.
BULK + DELTABulk enrichment, changed-record feeds, scheduled exports, and integration-specific delivery patterns for higher-volume workflows.
MCP + AI TOOLSExpose narrowly defined tools for property, location, market, rent, comps, and risk instead of making an agent parse pages.
WHITE LABEL + WEBHOOKSWhite-label data infrastructure, event-driven updates, direct onboarding, and founder-level integration support.
An appraisal product may want a single endpoint that begins with coordinates, resolves the parcel, maps the property type to its existing model, returns commercial fields and geometry, and excludes investor-specific signals. That can be the endpoint.
GET /v1/custom/appraisal-context?lat=&lng=
{
"parcel_id": "...",
"property_type": "COMMERCIAL_RETAIL",
"boundary": { "type": "Polygon" },
"owner": { ... },
"valuation": { ... },
"tax": { ... },
"sale_history": [ ... ],
"commercial_fields": { ... },
"source": { ... }
}
Bring your target counties, sample coordinates or parcel IDs, commercial property dictionary, required fields, expected volume, and preferred JSON shape. We will scope the standard routes, custom endpoint, and coverage plan around the real integration.
Every plan includes REST API access, the customer-safe MCP connector, and the interactive workspace for testing, key management, and usage visibility. Choose the request volume and integration depth your product needs. Global coverage begins at Scale $499/month; Great Britain, New Zealand, Australia, and Estonia are live today and additional countries will be added as coverage is productionized. Annual plans save 15%+ and lock in your rate for 12 months.
Most teams assemble separate parcel, assessor, rent, comps, flood, environmental-facility, demographic, and risk providers—then own every join, schema mismatch, coverage gap, and failure path. PropData collapses that chain into one production contract.
{
"match": {
"level": "exact_bbl",
"canonical_id": "NYC-BBL-1008350041"
},
"property": {
"name": "Empire State Building",
"situs_address": "338 5 AVENUE",
"county_fips": "36061",
"bbl": "1008350041"
},
"official_record": {
"source": "NYC MapPLUTO",
"source_version": "26v1"
},
"field_depth": {
"official_source_fields": 103,
"populated_official_fields": 82
}
}
One API can support the resolution, geometry, property, market, and risk layers behind an entire application.
Turn a map click or GPS coordinate into a verified parcel, boundary, official identifier, owner record, and enrichment payload.
/property/by-location + /parcel-geometry
Connect imagery, inspections, measurements, and mobile field activity to the correct parcel and property context.
coordinates → parcel → property
Combine property characteristics, valuation, parcel geometry, flood, natural hazards, neighborhood, and provenance.
?enrich=full
Normalize property types, retrieve official assessor fields, generate comps, and shape responses around your existing data model.
/property + /comps + custom schema
Use boundaries, acreage, property type, value, flood and environmental context, affordability, and market demand signals.
geometry + property + market
Give developers and agents structured tools instead of scraped pages. Use the same account across REST applications and supported MCP clients while keeping coverage, usage, and source behavior consistent.
REST + CURSOR + CHATGPT + CLAUDE + MCP
Provide the U.S. counties or international markets your product depends on. PropData can locate official records, build source-native identity and routing, ingest the data, run live QA, and publish production coverage. Custom endpoints and response shapes are available for qualified integrations.
Technical evaluation should be direct. These are the questions that matter when property intelligence becomes part of a product, workflow, or AI system.
Discuss your architecture →PropData is independent property and geospatial infrastructure for software products and AI workflows. The current production footprint spans the United States, Great Britain, New Zealand, Australia, and Estonia, with a 166M+ U.S. parcel core plus source-native GB, NZ, Australian, and Estonian identity layers. Global coverage is growing, and source-specific fields and enrichment depth stay explicit in every market.
We begin with the workflow: your inputs, the decisions your product needs to make, priority markets, required fields, response contract, and delivery pattern. Teams can use standard REST and MCP routes, bulk delivery, or a custom endpoint designed around the existing system.
Yes. Qualified integrations can use custom routes and response shapes so field names, nesting, property-type mappings, and enrichment bundles align with an existing product contract instead of forcing a full application rewrite.
Yes. The same PropData account can support REST applications and compatible MCP clients, including supported Cursor, ChatGPT, and Claude workflows. This gives an agent structured property tools and controlled schemas instead of relying on scraped pages or unverified free text.
In the U.S., PropData separates the nationwide indexed parcel foundation from county-specific production validation and geometry availability. Great Britain, New Zealand, Australia, and Estonia use source-native identity and geospatial layers instead of forcing U.S. parcel conventions onto international data. Responses carry source and availability context, and Scale+ customers can bring international market priorities into the coverage roadmap.
Build on one commercial property-data relationship that already spans the U.S., Great Britain, New Zealand, Australia, and Estonia—and is designed to keep expanding. Resolve source-native property identities, return geometry and official records where available, attach market and risk intelligence, and deliver through REST, Cursor, ChatGPT, Claude, MCP, bulk, or a custom endpoint.