Endpoint-aware inputs with readable JSON and parsed responses on the homepage.
AI-NATIVE + API-FIRST
166M+ U.S. PARCEL RECORDS
ADDRESS · PARCEL ID · COORDINATES
REST · CURSOR · CHATGPT · CLAUDE · MCP
CUSTOM ENDPOINTS + DAILY COVERAGE EXPANSION
REST API + CURSOR + CHATGPT + CLAUDE·
ONE PROPERTY INTELLIGENCE LAYER
From any location
to verified property intelligence.
Now inside your AI.
Get API access from $79· Published limits · No base-tier sales gate
PropData is one property and geospatial intelligence layer for every way your team builds. Start with an address, parcel ID, or coordinates. Resolve the property against a 166M+ indexed U.S. parcel foundation, return verified geometry where available, and attach ownership, valuation, tax, sale, comps, rent, market, risk, and location context. Call it through REST—or connect the same PropData account to Cursor, ChatGPT, Claude, and other MCP clients. Use standard routes, bulk workflows, or commission a custom endpoint shaped around your product.
ONE KEY.Authorize once inside each supported client. Requests continue through your PropData account, usage limits, coverage rules, and source-transparent response layer.
REST API
Cursor
ChatGPT
Claude
MCP Clients
Custom Endpoints
Full API Reference & Integration Guide
Authentication, endpoint routes, response schemas, coordinate lookup, geometry, enrichment, MCP connections, usage, errors, and production implementation guidance.
Download the PDF Guide →
166M+Parcel Records Indexed
50States in the Data Layer
20+Production API Routes
DailyCoverage Expansion
County assessor + GIS + market + rent + flood + hazard + demographic + proprietary intelligence
Interactive response explorer
Market intelligence
REPRESENTATIVE
READY
MARKET SNAPSHOT
SCHEMA-AWARE · REPRESENTATIVE
✓10 interactive schemas
✓20+ production routes
✓Live with your API key
DEVELOPER PROOF YOU CAN INSPECT
The product makes the case.
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.
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.
Transparent API Pricing
Start at $79.
Go live without waiting on sales.
Choose monthly or annual access below and continue directly to secure Stripe checkout. Every plan includes production REST access, the customer-safe MCP connector, and the interactive workspace. Your API key activates immediately after payment.
SECURE STRIPE CHECKOUT · KEY ACTIVATES INSTANTLY
STARTER
$79 / MONTH
BILLED TODAY · CANCEL ANYTIME
ANNUAL OPTION$799 / yearSave $149+ annually
- 10,000 requests each month
- 20+ property, market, rent, comps, and risk routes
- REST, workspace, and customer-safe MCP access
- Address, parcel ID, coordinate, and geometry workflows
Stripe checkout · instant key activation
BUILDER
MOST POPULAR
$199 / MONTH
BILLED TODAY · CANCEL ANYTIME
ANNUAL OPTION$1,999 / yearSave $389+ annually
- 50,000 requests each month
- Everything in Starter plus
enrich=full - Historical, geospatial, and AI-ready workflows
- Priority support and priority county coverage requests
Stripe checkout · instant key activation
SCALE
$499 / MONTH
BILLED TODAY · CANCEL ANYTIME
ANNUAL OPTION$4,999 / yearSave $989+ annually
- 250,000 requests each month
- Everything in Builder plus bulk and batch workflows
- Higher-volume API, geospatial, and agent operations
- 10 API keys with email and Slack support
Stripe checkout · instant key activation
ENTERPRISE
$1,499 / MONTH
BILLED TODAY · CANCEL ANYTIME
ANNUAL OPTION$14,999 / yearSave $2,989+ annually
- Unlimited requests and API keys
- Everything in Scale plus white-label rights
- Custom endpoints, responses, and coverage planning
- Direct onboarding and founder-level implementation
Stripe checkout · instant key activation
Need a market we have not fully configured yet? Builder, Scale, and Enterprise customers can submit priority county requests. Approved markets enter the active sourcing, canonicalization, and QA queue.
DISCUSS PRIORITY COVERAGE →
AI-NATIVE PROPERTY INTELLIGENCE
One data layer.
Every place your team builds.
PropData 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.
CURSORCONNECTED
Build with live property tools inside Cursor.
Let Cursor resolve properties, compare markets, inspect comps, estimate rent, and use neighborhood intelligence while it writes your application.
ADD PROPDATA TO CURSOR →CHATGPTMCP READY
Bring verified property context into AI workflows.
Use customer-safe tools instead of pasting raw API responses or asking an assistant to infer property facts from unstructured pages.
VIEW CONNECTION GUIDE →CLAUDEMCP READY
Give agents a constrained property toolset.
Expose narrowly defined lookup, market, comp, rent, and neighborhood functions with explicit coverage and match status.
VIEW MCP DOCUMENTATION →REST + CUSTOMPRODUCTION
Keep complete control inside your product.
Call the API directly, run bulk workflows, request custom response contracts, or embed PropData invisibly beneath your own interface.
EXPLORE ENDPOINTS →
ONE ACCOUNT · ONE KEY · ONE USAGE PLAN
Each customer authorizes with their own PropData account. Requests continue through that customer’s existing plan, limits, coverage behavior, and usage reporting—regardless of whether the call begins in an application or a supported AI client.
CONNECT PROPDATA TO CURSOR
REMOTE MCP · OAUTH-PROTECTED · CUSTOMER-SAFE
01Get a PropData keyChoose a plan or use an approved evaluation account.
02Install the connectorUse the Cursor install action or add the MCP URL manually.
03Authorize securelyEnter the email and API key connected to your account.
04Ask for property dataCursor discovers the tools and calls them when relevant.
MANUAL CURSOR CONFIGURATION · mcp.json
{
"mcpServers": {
"propdata": {
"url": "https://propdata-mcp.sales-fd3.workers.dev/mcp"
}
}
}
SAFE BOUNDARY
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.
Developer Resource
Everything needed to evaluate
and integrate the API.
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.
DOWNLOADABLE PDF
PropData API Reference & Integration Guide
Keep it open during evaluation, share it with your engineering team, or use it to scope a custom integration.
PropData Real Estate OS
The API is the product.
The OS is the operating proof.
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.
Watch the Real Estate OS Live →
Explore the API Platform
Aggregate operating proof only. No raw records, addresses, owners, customers, source URLs, or credentials are exposed.
Availability notice: The public Real Estate OS may occasionally be temporarily paused or taken offline for priority platform updates, infrastructure upgrades, and dedicated client enrichment work. These maintenance windows are intentional; please check back shortly for the live operating view.
Fifteen verified production parcels
Six states. Twelve counties.
Fifteen exact parcel boundaries.
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.
15 VERIFIED PARCELS · OFFICIAL POLYGONS
The Product
The dashboard shows it.
The API powers it.
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 →01 / RESOLVE
Start with what your product already has.
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=
02 / MAP
Return the parcel, not just a pin.
Use GeoJSON boundaries, centroids, and bounding boxes for click-a-parcel selection, overlays, acreage analysis, site planning, and spatial intersections.
GET /v1/parcel-geometry
03 / ENRICH
Collapse multiple vendors into one call.
Attach ownership, valuation, taxes, sales, characteristics, comps, rent, flood, hazard, neighborhood, affordability, and risk context.
?enrich=full
04 / DEPLOY
Deliver it in the shape your system needs.
REST endpoints, MCP connectors, bulk workflows, delta feeds, white-label infrastructure, custom endpoints, and custom response shapes.
REST + MCP + BULK + CUSTOM
ONE PRODUCTION WORKFLOW
Map click / GPS / address
→
County + parcel resolution
→
Boundary + official ID
→
Property + market enrichment
→
Your application
166M+ U.S. Parcel Records
America, resolved.
One national property intelligence layer.
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, and investment intelligence through one platform.
166M+U.S. parcel records
50All U.S. states
16Live data sources
APIREST · MCP · Custom
ADDRESSNormalize → county → parcelResolve a street address into the canonical property record.
PARCEL IDExact identifier → official recordPreserve county-specific APNs, leading zeros, and BBLs.
COORDINATESPoint-in-polygon → boundaryTurn a map click or GPS point into parcel geometry and attributes.
NATIONAL PROPERTY GRAPH ACTIVE
America's independent parcel intelligence foundation
166M+ PARCELS
All 50 states indexed
✓Three supported resolution inputs
One national identity layer, 16 live intelligence sources, and explicit coverage status.
FROM ONE PROPERTY TO A NATIONAL PORTFOLIO
Resolve, enrich, analyze, and ship.
Replace fragmented vendors and brittle joins with one production layer built for property search, underwriting, mapping, automation, and AI.
IDENTITYAddress → Parcel
GEOSPATIALCoordinates → Boundary
INTELLIGENCEProperty → Market + Risk
DELIVERYREST · MCP · Custom
Coverage
166M+ parcel records.
Four distinct coverage layers.
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.
166M+
Indexed U.S. parcel records across all 50 states form the foundation for property identity, official parcel IDs, address resolution, ownership and valuation fields where published, market enrichment, and the county-by-county geospatial expansion now underway.
01 / MARKET INTELLIGENCE
Nationwide ZIP, state, and metro context
Rent benchmarks, listing velocity, inventory, affordability, demographics, appreciation, mortgage context, hazards, and market signals.
NATIONWIDE LAYER02 / PARCEL INDEX
166M+ indexed property and parcel records
The national foundation for addresses, official parcel identifiers, county routing, ownership, values, tax and sale fields where the official source publishes them.
50-STATE FOUNDATION03 / VERIFIED ASSESSOR ENRICHMENT
County-specific production validation
Exact-ID crosswalks, source-schema validation, row reconciliation, null preservation, duplicate checks, and repeated property-to-enrichment gates.
04 / COORDINATE + GEOMETRY
Map point to parcel boundary
County routing, point-in-polygon matching, GeoJSON boundaries, centroids, bounding boxes, and spatial workflows expanding through verified markets daily.
Coverage is exposed as metadata, not hidden behind a national yes/no badge. Customer priority counties can be added to the sourcing and verification queue.
VIEW COVERAGE JSON →
COUNTY-VERIFIED INFRASTRUCTURE
Coverage is not a checkbox.
It is an engineering system.
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.
No manufactured values.
When an official source does not publish a field, the API returns
Request priority markets →
null. A legitimate zero remains zero. Provenance, source identifiers, retrieval context, and deliberately empty fields can travel with the record.
01
Locate the official source
Assessor, tax, public-record, and GIS systems are identified and validated at the county level.
02
Canonicalize exact identifiers
Leading zeros, punctuation, alternate parcel IDs, and assessor-to-GIS crosswalks are preserved and tested.
03
Resolve points against geometry
Latitude and longitude are routed to the correct county and matched to parcel boundaries with point-in-polygon logic where configured.
04
Reconcile the whole county
Row totals, duplicates, geometry, null behavior, source fields, and geographic canaries are audited before release.
05
Repeat live production gates
Address, parcel-only, coordinate, geometry, and full-enrichment workflows are tested repeatedly. Uncertainty is quarantined, not guessed.
THE MISS-TO-COVERAGE FLYWHEEL
Every miss reveals where the network
should become stronger next.
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.
THE PRODUCT ADVANTAGE
Customer demand does not disappear into a support inbox. It helps prioritize official-source discovery, parcel crosswalks, county imports, geometry routing, and live production verification—so one customer’s hard problem can become reusable infrastructure for the entire network.
LANE 01 · SAFE RUNTIME RESPONSENO FABRICATION
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
LANE 02 · COVERAGE EXPANSION SIGNALDEMAND → ROADMAP
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
Capture the exact failure stage
Address, parcel ID, coordinates, geometry, assessor join, or enrichment.
Rank by customer and market demand
Builder+ requests and repeated production gaps inform the active queue.
Locate the official county systems
Assessor, tax, public record, GIS, and exact source schemas.
Preserve identifiers and joins
Leading zeros, punctuation, alternate IDs, geometry links, and null behavior.
Run countywide and live gates
Row reconciliation, duplicates, canaries, point-in-polygon, and repeated chains.
Promote reusable infrastructure
The repaired route improves every future customer using that market.
BUILDER+ CUSTOMER COVERAGE PRIORITY
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.
Built Under Production Pressure
Real customer workflows are shaping the infrastructure.
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.
THE INPUTLatitude and longitude from a map-first customer workflow—not a clean mailing address.
THE HARD PARTCounty GIS and assessor systems frequently use different identifiers, schemas, geometries, and formatting rules.
THE OUTPUTVerified parcel identity, boundary, official record, provenance, and full enrichment through a reusable API chain.
THE FLYWHEELEvery county-level repair strengthens the same infrastructure for appraisal, insurance, solar, roofing, imagery, land, construction, and AI products.
Data Foundation
Official property records.
Market, risk, and geospatial layers.
One API.
PropData combines a 166M+ record U.S. parcel index across 50 states with direct county assessor and GIS records, market, rent, demographic, economic, flood, hazard, safety, and proprietary intelligence layers. The national parcel foundation matters—but the larger value is resolving a location to the correct parcel, returning verified geometry where available, and attaching the context your application needs without stitching together separate providers.
SOURCE 01
Fair Market Rents
U.S. Dept. of Housing & Urban Development
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.
SOURCE 02
Observed Rent Index
Zillow Research
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.
SOURCE 03
Market Metrics
Realtor.com Research
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.
SOURCE 04
Market Tracker
Redfin
Sale-to-list ratio, % sold above list, days to pending, months of supply. The sharpest demand signal in public real estate data.
SOURCE 05
ACS Demographics
US Census Bureau
Vacancy rates, renter %, median income, rent-to-income ratio, poverty rate, unemployment. Affordability context nobody else includes at this price point.
SOURCE 06
FRED Macro Data
Federal Reserve Bank of St. Louis
Mortgage rates, shelter inflation, national vacancy rate, and housing starts. National economic context alongside local market data.
SOURCE 07
House Price Index
FHFA — Federal Housing Finance Agency
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.
SOURCE 08
Building Permits
US Census Bureau BPS
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.
SOURCE 09 — PROPRIETARY
PropData Estimate Engine
PropTechUSA.ai
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.
SOURCE 10 — OWN PIPELINE
County Assessor + GIS Records
PropTechUSA.ai Direct Ingest
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.
SOURCE 11 — PROPRIETARY
Comps Engine
PropTechUSA.ai Built
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.
SOURCE 12 — PROPRIETARY
Geospatial Resolver
PropTechUSA.ai Built
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.
SOURCE 13 — LIVE · NEW
Natural Hazard Risk Index
FEMA — National Risk Index v1.20
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.
SOURCE 14 — LIVE · NEW
Community Safety Score
NCES · Census ACS · FBI CDE · FEMA SOVI
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.
SOURCE 15 — LIVE · NEW
Opportunity Zones + USDA Rural
HUD · USDA Rural Development · Census ZCTA
Every ZIP in America flagged for federal Opportunity Zone designation and USDA rural loan eligibility. OZ investors defer capital gains taxes. USDA eligibility means zero-down financing. Two filters that change deal structure entirely.
SOURCE 16 — LIVE · NEW
FEMA Flood Hazard + Skip Trace
FEMA NFHL · Microsoft Building Footprints
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.
POWERED BY PROPDATA
The same data powers these platforms
REAL ESTATE INVESTING
Local Home Buyers USA
Nationwide home buying platform powered by PropData parcels and AI acquisitions.
HOME BUYER INTELLIGENCE
Intelligent Home Buying
AI-powered home buying guidance using live market data and neighborhood intelligence.
LANDLORD INTELLIGENCE
Intelligent Landlord
Rent optimization, tenant screening signals, and property management insights.
SHORT TERM RENTAL
Intelligent STR
STR market analysis, occupancy forecasts, and revenue intelligence for operators.
Infrastructure
Source ingestion.
County routing.
Edge API delivery.
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.
PropTechUSA.ai Infrastructure
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.
DEPLOYED + LIVE
KV Edge Cache
All market data cached at Cloudflare's edge. 7-day TTL. Sub-50ms reads globally.
031d6a9e — ACTIVE
Supabase Canonical Store
15+ normalized tables. ZORI, Realtor, Redfin, HUD FMR, Census ACS, FHFA HPI — ZIP, state, and metro tiers. Indexed for fast queries.
rlfyavnhbngwbldebrid
API Key Auth + Rate Limiting
Tiered access: Starter 50 req/hr, Builder 500 req/hr, Internal unlimited. Keys provisioned in KV instantly on signup.
STRIPE INTEGRATED
PropData — Built on PropTechUSA.ai's 200+ Worker Stack
HUD APIWeekly cron→Zillow S3Monthly CSV→Realtor + RedfinMonthly TSV→Census + FHFAAnnual / Quarterly→FRED APIWeekly live→ArcGIS Ingest166M+ parcels · Own pipeline→Ingestion WorkersNormalize + upsert→SupabaseCanonical store→KV CacheEdge — 7d TTL→propdata APIYour API key→Your App<50ms→HUD APIWeekly cron→Zillow S3Monthly CSV→Realtor + RedfinMonthly TSV→Census + FHFAAnnual / Quarterly→FRED APIWeekly live→ArcGIS Ingest166M+ parcels · Own pipeline→Ingestion WorkersNormalize + upsert→SupabaseCanonical store→KV CacheEdge — 7d TTL→propdata APIYour API key→Your App<50ms
What the API Delivers
Six infrastructure layers.
One integration.
The dashboard demonstrates the response. Production teams integrate the API and select only the layers their workflow needs.
ONE-CALL DUE DILIGENCE
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.
Resolution LayerAddress / Parcel / Coordinates
Geospatial LayerBoundary / Centroid / BBox
Property LayerOwner / Value / Tax / Sale
Intelligence LayerComps / Rent / Risk / Market
Delivery LayerREST / MCP / Bulk / Delta
Enterprise LayerCustom Endpoints / White Label
23 routes shown below.One API key · REST + MCP · Custom contracts available
Endpoints
23 production routes are represented below—including coordinate lookup, parcel geometry, enrichment, intelligence, delta delivery, operational visibility, and MCP. Custom routes extend this surface around a customer's exact workflow.
GET/v1/marketMarket intelligence
?zip=55104 | ?state=MN | ?metro=Minneapolis
Rent, listing, demand, affordability, macro, FHFA, FRED, and investor signals
Rent, listing, demand, affordability, macro, FHFA, FRED, and investor signals
GET/v1/rentRent benchmarks
?zip=55104 | ?state=MN
Zillow ZORI, HUD FMR by bedroom, rent trend, confidence, and source metadata
Zillow ZORI, HUD FMR by bedroom, rent trend, confidence, and source metadata
GET/v1/listingListing velocity
?zip=55104 | ?state=MN
Median listing price, DOM, inventory, new listings, price reductions, and price per sqft
Median listing price, DOM, inventory, new listings, price reductions, and price per sqft
GET/v1/estimateRent AVM
?zip=55104&beds=2 | ?state=MN&beds=3
Low, mid, high rent range with confidence and methodology breakdown
Low, mid, high rent range with confidence and methodology breakdown
GET/v1/propertyProperty lookup
?address=123+Main+St&zip=55104 | ?parcel=27123
Official parcel identifiers, ownership, situs and mailing addresses, valuation, taxes, sales, and property characteristics
Official parcel identifiers, ownership, situs and mailing addresses, valuation, taxes, sales, and property characteristics
GET/v1/property?enrich=fullFull due diligence
?parcel=...&enrich=full
Core property record plus tax, equity context, comps, rent, flood, hazard, neighborhood, affordability, risk flags, and investment scoring
Core property record plus tax, equity context, comps, rent, flood, hazard, neighborhood, affordability, risk flags, and investment scoring
GET/v1/property/by-locationCoordinate lookup
?lat=25.8990225371643&lng=-80.237689454084&include_geometry=1
Lat/lng to county/FIPS to point-in-polygon parcel match where GIS coverage is configured
Lat/lng to county/FIPS to point-in-polygon parcel match where GIS coverage is configured
GET/v1/parcel-geometryParcel geometry
?county_fips=27053&parcel=27-117-21-14-0085
GeoJSON boundary, centroid, bbox, source, and coverage status
GeoJSON boundary, centroid, bbox, source, and coverage status
GET/v1/compsComps engine
?zip=55104&beds=3 | ?parcel=...
Comparable records ranked by price, sqft, recency, beds, and location context
Comparable records ranked by price, sqft, recency, beds, and location context
GET/v1/geocodeGeocode
?address=123+Main+St+Saint+Paul+MN | ?zip=55104
Address or ZIP lookup from PropData's own database
Address or ZIP lookup from PropData's own database
GET/v1/neighborhoodNeighborhood profile
?zip=55104 | ?city=Albany&state=NY&limit=20
Demographics, housing, safety, schools, affordability, and hazard context
Demographics, housing, safety, schools, affordability, and hazard context
GET/v1/zip-intelZIP intelligence
?zip=55104
Market scores, vacancy, yield, unemployment, appreciation, and AI investment summary
Market scores, vacancy, yield, unemployment, appreciation, and AI investment summary
GET/v1/state-intelState signal
?state=MN
BUY/HOLD/AVOID signal, friction score, top metros, risk index, and market trend context
BUY/HOLD/AVOID signal, friction score, top metros, risk index, and market trend context
GET/v1/property/deltaProperty delta
?since=2026-06-01T00:00:00Z&state=MN
Changed property records with cursor pagination
Changed property records with cursor pagination
GET/v1/property/coverageCoverage
No required params
Active assessor coverage and county availability metadata
Active assessor coverage and county availability metadata
GET/v1/skip-traceSkip trace
?address=123+Main+St&zip=55104 | ?state=MN
Owner contact, mailing address, equity, and lead status where available
Owner contact, mailing address, equity, and lead status where available
GET/v1/preforeclosurePre-foreclosure
?zip=55104 | ?state=MN
Notice date, auction date, case number, lender, default amount, and assessed value
Notice date, auction date, case number, lender, default amount, and assessed value
GET/v1/preforeclosure/deltaForeclosure delta
?since=2026-06-01T00:00:00Z&state=TX
Updated foreclosure records with cursor pagination
Updated foreclosure records with cursor pagination
GET/v1/changelogChangelog
No auth required
Versioned endpoint additions, fixes, source updates, and MCP/AI connector releases
Versioned endpoint additions, fixes, source updates, and MCP/AI connector releases
GET/v1/statsLive stats
No auth required
Live parcel count and API stats
Live parcel count and API stats
GET/v1/usageUsage
API key required
Current key usage, tier, limits, and reset metadata
Current key usage, tier, limits, and reset metadata
GET/v1/healthHealth
No auth required
API status, version, source health, plan mapping, and freshness metadata
API status, version, source health, plan mapping, and freshness metadata
MCPpropdata-mcpAI connector
https://propdata-mcp.sales-fd3.workers.dev/mcp
OAuth-protected connector for Cursor, supported ChatGPT and Claude workflows, and compatible MCP clients using each subscriber's own PropData key
OAuth-protected connector for Cursor, supported ChatGPT and Claude workflows, and compatible MCP clients using each subscriber's own PropData key
Latest: /v1/property/by-location supports coordinate-to-parcel workflows. Successful spatial matches return match_level=point_in_polygon and coverage_status=matched.
Developer Quickstart
One key.
Production JSON everywhere.
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.
THREE PRODUCTION WORKFLOWS · ONE API KEYcURL
# 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"
20+ routesProduction API surface
/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 + MCPPlatform Capabilities
More than parcels.
A complete property data layer.
Use 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.
LayerWhat it doesPrimary routes
Identity + Resolution
Resolve addresses, official parcel IDs, ZIPs, county FIPS, and coordinates against a 166M+ indexed U.S. parcel foundation and the correct county workflow.
/v1/property
/v1/geocode
/v1/property/by-location
Parcel Geometry
Return GeoJSON boundaries, centroids, and bounding boxes for mapping and spatial workflows.
/v1/parcel-geometry
Core Property
Ownership, situs and mailing addresses, valuation, taxes, sales, year built, living area, lot size, acreage, and property type.
/v1/property
Full Enrichment
Attach equity context, comps, rent, flood, hazards, neighborhood, affordability, risk flags, and investment scoring.
?enrich=full
Market + Rent
ZIP, state, and metro intelligence, rent benchmarks, estimate ranges, inventory, velocity, affordability, appreciation, and macro context.
/v1/market
/v1/rent
/v1/estimate
Risk + Location Context
Flood zones, natural-hazard exposure, safety, schools, demographics, opportunity-zone and rural-eligibility context.
/v1/neighborhood
/v1/zip-intel
/v1/state-intel
Operational Data
Property changes, pre-foreclosure updates, coverage visibility, usage, health, and machine-readable changelogs.
/v1/property/delta
/v1/preforeclosure/delta
/v1/changelog
AI + Enterprise Delivery
MCP connectors, bulk workflows, customer-specific endpoints, custom response contracts, webhooks, white-label infrastructure, priority county sourcing, and direct integration support.
REST + MCP + CUSTOM
API Workspace
The dashboard is a working demonstration of the data layer.
Use it to inspect responses, manage keys, monitor usage, and test workflows. Customer-facing products should call the PropData API directly.
PropData vs RentCast, ATTOM, Regrid, BatchData, Mashvisor & Cotality
Competitors sell a slice.
PropData sells the infrastructure.
The point of this comparison is not to celebrate six other vendors. It is to show what your team is still missing after buying only property records, only parcel geometry, only skip trace, only rental analytics, or an enterprise bundle assembled across several separate products.
PropData’s value: one API platform, one live Real Estate OS, one implementation relationship, transparent entry pricing, custom endpoints, and an engineering roadmap that Builder+ customers can help prioritize.
THE NORMAL MULTI-VENDOR STACK
Five contracts to build one property product.
Teams commonly stitch together separate vendors for property records, geometry, contact enrichment, rental analytics, risk, public records, and AI connectivity—then maintain the joins, keys, billing, licensing, and failure modes themselves.
Property / AVM
Parcel geometry
Skip trace
Rent analytics
Risk + public records
AI + custom delivery
THE PROPDATA STACK
One API. One OS. One roadmap.
Start from an address, parcel ID, ZIP, or coordinates. Resolve the property, draw the boundary, enrich the record, attach market and risk context, deliver it through REST, MCP, bulk, delta, webhook, or a custom contract—and watch the operating system strengthening underneath it.
166M+ parcel indexCoordinate → parcel
Geometry + assessorComps + rent + market
Hazard + neighborhoodPublic-record OS
MCP + delta + webhooksCustom endpoints
Published request economics favor PropData.
Included requests per dollar at each provider’s first published paid monthly tier:
10,000 successful monthly calls.
Published self-service pricing and listed overages produce this benchmark:
PROPDATA$79
RENTCAST$349
MASHVISOR$2,699
Pricing comparison only. Products do not expose identical fields, licensing rights, service levels, or response sizes.
What you still need after buying them.
Competitor names remain because buyers search for them. The sales story is the missing infrastructure PropData consolidates.
After RentCast
You have a polished property, AVM, comps, listings, and market API. You may still need county-verified parcel geometry, a public production OS, public-record intelligence, MCP, delta feeds, custom response contracts, and customer-prioritized county buildout.
PROPDATA ADDS THE GEOSPATIAL + OS + CUSTOM INFRASTRUCTURE LAYER.
After Regrid
You have a serious parcel and spatial layer. You may still need rent estimates, market and macro intelligence, comps, hazards, neighborhood context, public records, investment signals, and a unified property enrichment response.
PROPDATA TURNS THE PARCEL INTO A COMPLETE PROPERTY-INTELLIGENCE WORKFLOW.
After BatchData
You have strong owner contacts, compliance tools, address services, and monitoring. You may still need parcel boundaries, point-in-polygon matching, county assessor routing, market and rent layers, hazards, and the live OS that builds new jurisdictions.
PROPDATA ADDS THE MAP, ASSESSOR, MARKET, RISK, AND COVERAGE ENGINE.
After Mashvisor
You have investment and rental analytics. You may still need an independent parcel foundation, geometry, direct county records, public-record intelligence, MCP, delta delivery, white-label infrastructure, and custom endpoint engineering.
PROPDATA IS THE DATA AND INFRASTRUCTURE LAYER UNDER THE ANALYTICS.
After ATTOM
You have a broad established property-data catalog. PropData offers transparent entry pricing, direct builder access, the live Real Estate OS, custom endpoints, a modern location-to-parcel chain, and customer-prioritized county work without starting from an opaque enterprise bundle.
PROPDATA COMPETES ON SPEED, TRANSPARENCY, FLEXIBILITY, AND DIRECT EXECUTION.
After Cotality
You have an institutional property ecosystem with broad delivery options. PropData gives emerging and scaling platforms a lower-friction path to comparable workflow categories, public pricing, founder-level integration, custom routes, and visible production proof at os.proptechusa.ai.
PROPDATA MAKES PROPERTY INFRASTRUCTURE ACCESSIBLE BEFORE YOU NEED ENTERPRISE PROCUREMENT.
Why PropData replaces more of the stack
7 PROVIDERS · 13 CAPABILITIESScroll horizontally to compare every column · Public materials reviewed July 25, 2026
| Capability | PropData | RentCast | ATTOM | Regrid | BatchData | Mashvisor | Cotality |
|---|---|---|---|---|---|---|---|
| Transparent paid entry plan | $79 / 10K | $74 / 1K | Plan dependent | Plan dependent | Contact sales | $129 / 500 | Contact sales |
| 166M+ independent U.S. parcel index | Yes | 150M+ properties | 160M+ properties | 160M+ parcels | Public count not stated | Analytics-led | Enterprise scale |
| Address + parcel ID + true coordinate-to-parcel | All three | Property + coordinate workflows | Lat/lon + radius | Point + radius + polygon | Geocode / reverse geocode | Not highlighted | Spatial products |
| Parcel geometry inside broader intelligence workflow | County verified + expanding | Not highlighted | Boundary products | Core geometry product | Not highlighted | Not highlighted | Core spatial products |
| Property + comps + rent + market + macro | One platform | Property + AVM + trends | Multiple products | Not rent / market led | Not core | Rental analytics core | Multiple enterprise products |
| Hazard + flood + neighborhood + affordability | Integrated | Not full stack | Separate products | Spatial context | Not core | Neighborhood analytics | Enterprise products |
| Public-record intelligence lane | Cases, violations, citations, enforcement | Not highlighted | Foreclosure / permit data | Not core | Permit / lien / monitoring | Not core | Broad public-record sources |
| Live public Real Estate OS | Operating in public | Not publicly offered | Not publicly offered | Not publicly offered | Not publicly offered | Not publicly offered | Not publicly offered |
| Visible customer priority lanes | Builder+ roadmap input | Not publicly offered | Not publicly offered | Sales / support | Not publicly offered | Not publicly offered | Enterprise roadmap |
| MCP + AI-agent tools | Live MCP | Not highlighted | Not highlighted | MCP server | MCP server | Not highlighted | Enterprise MCP |
| Delta + monitoring + webhook delivery | Delta feeds + custom webhooks | Not highlighted | Enterprise feeds | Batch delivery | Monitoring push | Not highlighted | Cloud delivery |
| Custom endpoints + customer JSON contract | Core product | Enterprise inquiry | Enterprise packages | Enterprise delivery | Sales-led workflows | Enterprise only | Enterprise delivery |
| Best fit | One integrated builder stack | Property / AVM API | Broad enterprise property data | Parcel / spatial specialist | Contacts / compliance specialist | Rental analytics specialist | Institutional data ecosystem |
PropData vs RentCast
RentCast covers property records, owner details, AVMs, comps, listings, and market trends. PropData is the stronger consolidation play when the same product also needs point-in-polygon parcel resolution, geometry, broader market and federal layers, hazards, public records, MCP, delta delivery, custom endpoints, the live Real Estate OS, and Builder+ priority county work. Read the full comparison.
PropData vs Regrid
Regrid is centered on parcel geography. PropData extends the workflow after the boundary: owner and assessor intelligence, valuation, comps, rent, market, hazard, neighborhood, public records, AI connectors, custom response contracts, and a visible operating system improving the data network underneath the API.
PropData vs BatchData
BatchData is contact, compliance, address-service, and monitoring infrastructure. PropData is the broader map-to-intelligence platform when the application also requires true parcel resolution, geometry, assessor data, market and rent intelligence, risk, public records, custom endpoints, and customer-directed county expansion.
PropData vs Mashvisor
Mashvisor provides investment-oriented rental and neighborhood analytics. PropData is the infrastructure layer underneath a wider range of real estate software: parcels, coordinates, geometry, assessor data, comps, rent, markets, hazards, public records, MCP, delta feeds, and custom APIs. Read the full comparison.
PropData vs ATTOM
ATTOM is a broad established property-data catalog. PropData sells a faster, more transparent path for builders: public entry pricing, direct integration access, a live location-to-parcel chain, a public Real Estate OS, custom response contracts, and a Builder+ priority queue for the counties the product actually needs.
PropData vs Cotality
Cotality is a large institutional property ecosystem. PropData gives startups and scaling platforms an accessible API-first alternative with transparent pricing, founder-level implementation, custom routes, public production proof, customer-prioritized county coverage, and one integrated property, market, geospatial, risk, public-record, and AI stack.
Official product and pricing pages reviewed July 25, 2026:
RentCast ·
ATTOM ·
Regrid ·
BatchData ·
Mashvisor ·
Cotality.
Competitor products and terms can change. “Not publicly highlighted” means the reviewed public materials did not establish the feature; it is not proof that a separate product or contract cannot provide it. All trademarks belong to their respective owners. No endorsement or affiliation is implied.
Stop paying six vendors to build one product.
Bring your current contracts, endpoints, required fields, counties, usage, and target response. We will show you what PropData can consolidate, where a specialist may still make sense, and what custom route would remove the most engineering work.
Custom API Studio
Your workflow should not bend
around somebody else's schema.
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 ROUTESOne endpoint for the complete workflow
Combine coordinate resolution, parcel geometry, assessor fields, comps, flood, rent, and risk into one purpose-built request.
RESPONSE SHAPESMatch your existing schema
Rename fields, flatten nested objects, map property types to ATTOM or internal dictionaries, and return only the fields your product consumes.
PRIORITY COVERAGESource the counties your customers need
Official-source discovery, county routing, canonical IDs, imports, geometry, reconciliation, and live QA can follow a qualified customer roadmap.
BULK + DELTAMove more than one property at a time
Bulk enrichment, changed-record feeds, scheduled exports, and integration-specific delivery patterns for higher-volume workflows.
MCP + AI TOOLSGive agents structured property tools
Expose narrowly defined tools for property, location, market, rent, comps, and risk instead of making an agent parse pages.
WHITE LABEL + WEBHOOKSShip PropData invisibly inside your product
White-label data infrastructure, event-driven updates, direct onboarding, and founder-level integration support.
Example Customer Contract
Ask for the JSON you wish existed.
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": { ... }
}
FROM REQUIREMENTS TO A PRODUCTION CONTRACT
BOOK WITH JUSTIN →
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.
Unified Access Pricing
Pay for intelligence once.
Use it everywhere you build.
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. Annual plans save 15%+ and lock in your rate for 12 months.
Annual plans now live
Pay once, save 15%+, and keep the same API access for a full year. Built for serious builders, dashboards, AI agents, and long-term data workflows.
API-first by design
The workspace is included as an interactive demo and account console. Production products connect directly to REST, Cursor, ChatGPT, Claude, another compatible MCP client, a bulk workflow, or a custom enterprise integration.
Discuss an integration
Bring your target counties, sample coordinates, required fields, expected volume, or custom response contract. Book an integration call.
Need to validate a workflow?
Qualified teams can request a capped evaluation key for a documented integration or county-coverage test. Bulk extraction and production-scale usage require a paid plan.
Starter
$79
per month
Billed today · cancel anytime
$799 / year
Save $149+ annually
- 10,000 requests/month
- Access to 20+ endpoint routes
- Customer-safe MCP access for Cursor and compatible AI clients
- Full market intelligence
- Neighborhood + FEMA data
- Address, parcel ID, and coordinate lookup
- Comps engine access
- Geocoding
- Coordinate-to-parcel resolution where configured
- Parcel geometry, centroid, and bbox where configured
- Live changelog + usage endpoints
- enrich=full - Builder+
- Historical data - Builder+
Monthly billed today · Cancel anytime · Annual billed once
Builder
$199
per month
Billed today · cancel anytime
$1,999 / year
Save $389+ annually
- 50,000 requests/month
- Everything in Starter
- enrich=full unlocked
- Full-enrichment workflows through REST and supported AI clients
- Tax, equity context, comps, rent, flood, hazard, neighborhood, and investment scoring
- Historical data
- Production coordinate-to-parcel workflows
- Parcel geometry workflows
- Priority county coverage requests
- Priority email support within 24 hours
- 3 API keys
- Slack support - Scale+
Monthly billed today · Cancel anytime · Annual billed once
Scale
$499
per month
Billed today · cancel anytime
$4,999 / year
Save $989+ annually
- 250,000 requests/month
- Everything in Builder
- Bulk and batch workflows
- Higher-volume API and AI-agent workflows
- Email + Slack support within 4 hours
- 10 API keys
- Higher-volume geospatial and enrichment workflows
- Priority issue review
- 99.0% uptime SLA
- Cancel anytime
Monthly billed today · Cancel anytime · Annual billed once
Enterprise
$1,499
per month
Billed today · cancel anytime
$14,999 / year
Save $2,989+ annually
- Unlimited requests
- Everything in Scale
- Direct Supabase access
- White-label rights
- 99.9% uptime SLA
- Direct founder access
- Unlimited API keys
- Custom onboarding
- Priority county sourcing and coverage engineering
- Custom endpoint and response-contract design
- MCP, AI-agent, bulk, webhook, and white-label support
Monthly billed today · Cancel anytime · Annual billed once
ONE API VS. A FRAGMENTED PROPERTY STACK
Stop stitching property data together.
Resolve it once.
Most teams assemble separate parcel, assessor, rent, comps, flood, demographic, and risk providers—then own every join, schema mismatch, coverage gap, and failure path. PropData collapses that chain into one production contract.
TYPICAL PROPERTY STACK7+providers · keys · schemas · failure paths
PROPDATA1key · contract · response · support path
WORKFLOWTYPICAL STACKPROPDATA
Property identitySeparate parcel + assessor joinsAddress, APN, or coordinates → canonical record
Financial contextTax, sale, value, and equity logic assembled downstreamSource-aware property and financial fields
Market intelligenceSeparate comps, rent, demographic, and macro feedsComps, rent, market, neighborhood, and affordability
Geometry + riskParcel boundary, flood, and hazard vendors reconciled laterVerified geometry plus flood, hazard, and location context
DeliveryMultiple auth models, schemas, limits, and support queuesREST, MCP, bulk, delta, or custom contract
{
"match": {
"input": "parcel_id",
"county_fips": "12086",
"match_level": "exact"
},
"parcel": {
"official_id": "...",
"geometry": {
"type": "Polygon",
"centroid": [ -80.23, 25.89 ]
}
},
"property": {
"owner": {},
"valuation": {},
"tax": {},
"sale_history": [],
"characteristics": {}
},
"enrichment": {
"comps": [],
"rent_estimate": {},
"flood": {},
"hazards": {},
"neighborhood": {},
"risk_flags": [],
"investment_score": {}
},
"provenance": {
"official_source": "...",
"retrieved_at": "...",
"unavailable_fields": []
}
}
Representative response shape. Available fields vary by official source and verified county coverage.
Production Use Cases
Infrastructure for products
that begin with a property or a point on a map.
One API can support the resolution, geometry, property, market, and risk layers behind an entire application.
MAP / GIS
Mapping and parcel-selection products
Turn a map click or GPS coordinate into a verified parcel, boundary, official identifier, owner record, and enrichment payload.
/property/by-location + /parcel-geometry
IMAGERY / FIELD
Drone, roofing, solar, and field-service software
Connect imagery, inspections, measurements, and mobile field activity to the correct parcel and property context.
coordinates → parcel → property
RISK / INSURANCE
Insurance and due-diligence workflows
Combine property characteristics, valuation, parcel geometry, flood, natural hazards, neighborhood, and provenance.
?enrich=full
APPRAISAL / VALUATION
Appraisal, valuation, and commercial-property tools
Normalize property types, retrieve official assessor fields, generate comps, and shape responses around your existing data model.
/property + /comps + custom schema
SITE / LAND
Land, construction, and site-selection platforms
Use boundaries, acreage, property type, value, flood and environmental context, affordability, and market demand signals.
geometry + property + market
AI / AUTOMATION
Cursor, ChatGPT, Claude, and automated workflows
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
Customer-Directed Coverage
Your priority markets can shape the roadmap.
Provide the counties your product depends on. PropData can locate official records, build canonical routing, ingest the data, run live QA, and publish verified coverage. Custom endpoints and response shapes are available for qualified integrations.
Do not put another data-ingestion project on your roadmap.
Put PropData underneath the product—and inside your AI.
Resolve addresses, parcel IDs, and coordinates. Return geometry. Attach official property records, market context, comps, rent, flood, hazards, neighborhood intelligence, risk, and provenance. Build through REST, Cursor, ChatGPT, Claude, MCP, bulk, or a custom endpoint.