The property data layer
behind what you build.

Your team should build the product—not spend months rebuilding the data layer underneath it.

Real estate data is fragmented across county assessors, GIS layers, federal datasets, market feeds, incompatible identifiers, changing schemas, and geographic coverage gaps. The expensive part is not making one API request. It is making all of those sources behave like one dependable system.

PropData turns that engineering burden into infrastructure. One authenticated platform can resolve a property, identify its parcel, attach county and market context, return parcel geometry where configured, rank comps, expose risk and neighborhood intelligence, monitor changed records, and connect the same capabilities to supported AI workflows.

That is the leverage: faster product launches, fewer vendor integrations, a smaller internal data-maintenance burden, and one source-aware response your application can turn into underwriting, research, mapping, acquisitions, lending, insurance, CRM, or AI experiences.

A clean API surface for messy real estate data.

Use the direct base URL, send your API key in the x-api-key header, and receive structured JSON with source and coverage context. All production paths begin with /v1/.

// Coordinate to parcel with optional GeoJSON geometry
const base = 'https://propdata-api-worker.sales-fd3.workers.dev';
const path = '/v1/property/by-location?lat=25.8990225&lng=-80.2376894&include_geometry=1';

const response = await fetch(base + path, {
  headers: { 'x-api-key': 'pd_live_YOUR_KEY' }
});

if (!response.ok) throw new Error('PropData request failed');
const data = await response.json();

console.log({
  matchLevel: data.match_level,
  coverage: data.coverage_status,
  parcel: data.parcel,
  geometry: data.geometry
});

import requests

BASE = "https://propdata-api-worker.sales-fd3.workers.dev"
HEADERS = {"x-api-key": "pd_live_YOUR_KEY"}

response = requests.get(
    BASE + "/v1/market",
    headers=HEADERS,
    params={"zip": "55104"}
)
response.raise_for_status()
market = response.json()

# Keep attribution and source periods with customer-facing outputs.
print(market.get("snapshot"))
print(market.get("sources"))
print(market.get("generated_at"))

# Coverage metadata
curl "https://propdata-api-worker.sales-fd3.workers.dev/v1/property/coverage" -H "x-api-key: pd_live_YOUR_KEY"

# Property lookup with full enrichment where supported
curl "https://propdata-api-worker.sales-fd3.workers.dev/v1/property?address=123+Main+St&zip=55104&enrich=full" -H "x-api-key: pd_live_YOUR_KEY"

# Changed records since a timestamp
curl "https://propdata-api-worker.sales-fd3.workers.dev/v1/property/delta?since=2026-07-01T00:00:00Z&state=MN" -H "x-api-key: pd_live_YOUR_KEY"

// OAuth-protected connector for supported AI clients
SERVER  https://propdata-mcp.sales-fd3.workers.dev/mcp
AUTH    OAuth
ACCESS  Subscriber's own PropData API key

// Agent workflows can combine:
property lookup
coordinate-to-parcel resolution
market and rent intelligence
comps and parcel geometry
coverage-aware explanations

See the live documentation or download the 27-page API reference guide for authentication, parameters, response shapes, coverage, and troubleshooting.

One company. Two serious developer APIs.

PropData powers real estate intelligence. PropSports applies the same infrastructure-first approach to live sports data, Statcast, player props, weather, umpires, and model odds.