PropDataAPI Workspace
Checking API 225M+ property identities 24 production routes Verified coverage expands daily
2026.08 API Guide ↗
Preview mode. Request Lab network calls are blocked. Connect a PropData key to load account telemetry, then deliberately switch to Production before making a live request.
Developer control plane

Everything around the API.
Nothing pretending to be the product.

Manage access, inspect usage, run real requests, understand coverage, connect AI clients, and get production support. Your application remains the customer experience.

Read API Docs
API-first by design

Your product owns the interface. PropData supplies the intelligence.

Resolve an address, parcel ID, UPRN, or coordinate into a source-aware property identity across the U.S., Great Britain, New Zealand, Australia, and Estonia. Then attach the geometry, ownership, valuation, market, risk, provenance, and enrichment layers available for that source through one account.

ONE REQUEST · CUSTOMER-SAFE JSONPREVIEW
GET /v1/property?county_fips=36061&parcel=1008350041&enrich=full
PARCELCOMMUNITYEPA PROXIMITYDECISION LAYERS
REST · Cursor · ChatGPT · Claude · MCPONE KEY
Production verified · 2026-08

Community + Environmental Intelligence is live inside Full Enrich.

One property request now resolves source-aware block-group context, tract-level incentive screening, and national EPA FRS facility proximity. The core property response stays reliable; unavailable fields remain null or explicitly unavailable with coverage and provenance attached.

2026 Census PDBACS 2020–2024242,336 block groupsEPA FRS · 2026-08-01
Open API guide ↗
01 · Precision layer Block Group Intelligence block_group_intelligence

Population, socioeconomic, housing, tenure, digital access, and exact 2020 Census benchmarks with published margins of error.

02 · Incentive layer Tract Intelligence tract_intelligence

Opportunity Zone eligibility screening, NMTC/QCT, rurality, assisted housing, employment, FHA, and curated tract context.

One-call property extensionCommunity + EPA context inside enrich=full

A root geography summary identifies the tract and block group, while verified parcel coordinates can attach EPA facility-proximity coverage and results to the same returned property record.

BUILDER+ · LIVE
New national layer · production live EPA FRS facility proximity now ships inside enrich=full.

Verified parcel coordinates are screened against the indexed EPA Facility Registry Service snapshot with distance-ranked matches, program associations, coverage, provenance, and limitations.

5.3MFederal source rows
4.18MCoordinate-bearing records
2026-08-01Source release

Screening limitation: proximity does not prove contamination, liability, or current regulatory status. Records without coordinates cannot support a favorable universal negative.

Live contractVerified against production
Tract route36061007600HTTP 200 · coverage available
Block-group route360610076001HTTP 200 · coverage available
Empire Full Enrich36061 · 1008350041Community + EPA verified
Current data releasesProduction truth, with status attached.
National EPA FRS proximityLive

Authenticated production canary passed for 36061 · 1008350041: coverage available from a verified parcel centroid, with five distance-ranked results returned.

Bexar County · 480292026 validation

Stale 2019 metadata is corrected to the current 2025 production roll. The 730,721-row official 2026 roll has passed bounded dry-run validation and remains labeled in progress until publication completes.

Current plan
Preview
Connect a key to load your account.
Monthly quota
/ —
Live usage not connected
Billing cycle reset
Reset metadata not connected.
Execution modePreview · zero callsProduction requests require an explicit mode change and Run action.
Billing resetNot reportedConnect an account to load authoritative reset metadata.
Session latencyNo samplesp95 is calculated only from Request Lab calls in this browser.
Credential protectionProtectedCredentials stay masked and are used only for deliberate API requests.
Primary credentialCopy deliberately; examples continue to use an environment variable.
Not connected
No API key connected

This browser never inserts the literal secret into a URL or quickstart. Customer-facing apps should call PropData from a trusted server or edge runtime.

Execution contextVerified states only—no pretend sandbox or connection claims.
Preview
ModePreview · live Request Lab calls blocked
APIHealth check pending
MCPOAuth available · client authorization not verified here
WebhooksNo delivery telemetry endpoint connected
Recent Request Lab activityLast eight explicit calls from this browser session—not fabricated account-wide traffic.
No requests yet
Run a request in Production mode to build a private, session-only diagnostic trail here.
Webhook & event deliveryOnly server-reported deliveries appear here; the workspace never fabricates event traffic.
Telemetry unavailable
No webhook delivery telemetry was returned by the authenticated usage contract.
Production quickstart
Environment variables keep keys out of source code

          
Base URL: propdata-api-worker.sales-fd3.workers.dev
Integration contract
What stays stable beneath your product
One connected credentialAutomatically sent in each route's supported PropData auth header
Ready
Canonical parcel identityCounty-aware identifiers and source provenance
Ready
Null-preserving responsesMissing data stays missing instead of becoming fiction
Ready
Coverage-aware geometryBoundaries where official GIS is configured
Ready
Two-level community contractBlock-group precision and tract-level incentives with explicit provenance
Live
Custom response contractsEnterprise schemas shaped around real workflows
Available
Interactive request lab

Build, run, and inspect a real API request.

Choose a production route, supply only the parameters you need, then inspect the exact HTTP response. Main endpoint requests run only when you press Run. Property and Full Enrich accept either an address with ZIP or an exact parcel identity.

Routes
24 requestable endpoints
GET
https://propdata-api-worker.sales-fd3.workers.dev/v1/market?zip=55101
Market intelligence

Market snapshot

RESPONSE
NOT RUN— MS— KB
EXPECTED SHAPE · illustrative fields onlyNo live rate-limit headers yet

            
Account telemetry

Usage you can reason about.

The authenticated usage contract reports plan consumption, allowance, remaining requests, reset time, and—when available—per-endpoint activity. Individual responses may also include worker-window rate-limit headers.

Manage billing
Authenticated plan window
requests
Connect a key to load usage
0
PREVIEW
Connect your key

Your subscription allowance and live rate-limit window will appear here without inventing unavailable monthly usage.

Requests this window
Reported by the authenticated /v1/usage route.
Remaining this window
Calculated from the reported limit.
Active endpoints
Routes present in the usage breakdown.
Endpoint activity
Breakdown supplied by the usage endpoint
Connect a key to load live endpoint activity.
Production surface

One API. 24 production routes.

Property resolution, parcel geometry, market and rent intelligence, block-group community profiles, tract incentives, national EPA FRS proximity, public-record signals, deltas, coverage, usage, health, and AI delivery are represented below. Custom endpoints extend this surface around your exact workflow.

Open API guide ↗
25 REST routes + MCP
Coverage model

Global identity. Source-level truth.

PropData separates global property identity reach from source-specific enrichment depth. U.S. assessor and GIS depth remains county-specific, while Great Britain, New Zealand, Australia, and Estonia use their own source-native property identity foundations and provenance.

Request a county
225M+
Property + parcel identities

The global identity foundation spanning the U.S., Great Britain, New Zealand, Australia, and Estonia.

5
Source-native markets

United States, Great Britain, New Zealand, Australia, and Estonia under one property intelligence layer.

166M+
U.S. parcel foundation

County-aware U.S. identity with assessor and GIS depth governed by source-level coverage.

Source-aware
Verified coverage expansion

Official county, national, state, and territory layers move through source-level publication gates.

Three coverage layers
Clear claims instead of a misleading yes/no map
PropData parcel coverage stackThree verified data layers align over one parcel polygon: canonical index, assessor enrichment, and GIS geometry.GISASSESSORINDEX
03GIS geometry

Verified polygon, centroid, and bounds only where county GIS routing has passed QA.

02Official assessor enrichment

Ownership, tax, valuation, sale, and building fields vary with the configured source.

01Canonical parcel index

County-aware parcel identity and location resolution form the national foundation.

FIVE LIVE PROPERTY IDENTITY MARKETS: United States · Great Britain · New Zealand · Australia · Estonia. Select the country in supported identity tools; source-native identifiers and provenance stay attached.
ESTONIA · LIVE: Use country=EE with a national cadastral ID or ADS-backed address.
Production rule: use /v1/property/coverage and response provenance to decide what your workflow can promise for a given county. A missing field remains null; coverage is never inferred from marketing language.
Federal overlay: EPA FRS proximity reports coverage independently from county assessor and GIS depth. It uses verified coordinates against the indexed 2026-08-01 snapshot and cannot turn records without coordinates into a favorable universal negative.
Live coverage response
/v1/property/coverage
Load the live coverage contract, then search locally by county or FIPS.
Inspect exact worker response
Connect a PropData API key, switch to Production, then choose “Load live coverage.”

This panel preserves the worker response exactly as returned.
AI-native delivery

The same property layer inside your code and your AI.

Use REST directly, connect compatible MCP clients, or commission a customer-specific response contract. Authentication, account controls, coverage rules, and usage stay unified underneath.

MCP connector status

PropData MCP uses OAuth in the client. This workspace can verify your REST key, but it will not claim Cursor, ChatGPT, or Claude is connected without a client authorization record.

OAUTH READY · CLIENT NOT VERIFIED
ConnectorPublished URL configuredThe workspace does not infer protocol health from a marketing link.
AccountREST account not connectedOAuth authorization still occurs independently inside each MCP client.
Client sessionNot observable hereA connected state appears only when server telemetry explicitly reports it.
CURSOR · ONE CLICK

Build with live property tools in your editor.

Resolve parcels, inspect geometry, compare markets, estimate rent, and call supported tools without leaving the development workflow.

Add to Cursor →
CHATGPT + CLAUDE

Connect compatible MCP workflows.

Bring PropData tools into supported AI clients while keeping production requests tied to the subscriber account and its limits.

REST + CUSTOM

Keep complete control in your product.

Call standard routes, run bulk or delta workflows, or define a response shape that drops directly into an existing schema.

{
  "mcpServers": {
  "propdata": {
    "url": "https://propdata-mcp.sales-fd3.workers.dev/mcp"
  }
  }
}
One account, controlled usage. Connecting an AI client does not create a second data product. Requests continue through the same PropData account, source-transparent response layer, coverage rules, and plan.
Credentials

Keep production access deliberate.

The workspace keeps the active key in memory for this session unless you explicitly choose to remember it on this device. Keys are never written into example source code or page URLs.

Connected credential
Used only for explicit requests from this browser
NOT CONNECTED
No API key connected
Quickstart examples use PROPDATA_API_KEY, not the literal credential.
The request lab sends the connected key only in the selected route's supported authentication header to the PropData API origin.
Disconnect removes both session and remembered browser copies.
Production handling
Recommended server-side pattern
# .env — never commit this file
PROPDATA_API_KEY=pd_live_...

# Runtime request
curl "$PROPDATA_URL/v1/property?parcel=..." \
  -H "x-api-key: $PROPDATA_API_KEY"
Do not expose a live key in browser code. This workspace is an account tool. Your customer-facing application should call PropData from a trusted server or edge function.
Current API pricing

Plans built around requests, not dashboard features.

The old consumer-dashboard tiers are gone. Every plan is an API plan; higher tiers add volume, deeper enrichment, more keys, priority coverage, delivery options, and integration support.

Coverage is a workflow, not a vague upsell. Builder, Scale, and Enterprise customers can submit priority county requests. Approved markets enter official-source discovery, parcel crosswalk, geometry routing, and live QA.
Implementation resources

Get from first request to production.

Use the API reference for contracts, the workspace for live testing, and direct support for county coverage or customer-specific payloads.

Downloadable PDF · Release 2026.08

The complete PropData API Reference & Integration Guide.

Everything your engineering team needs to evaluate the platform and move into production: authentication, the complete route surface, Full Enrich, live Community Intelligence, parcel geometry, MCP workflows, usage, errors, coverage rules, and implementation examples.

21Curated pages
25Requestable routes
17Data layers
2Community contracts
Open reference guide ↗ Download PDF
DOC

Web documentation

Browse the latest route reference, schemas, setup notes, and implementation examples in the documentation workspace.

Open documentation
API

Request Lab

Build a URL from supported parameters, make an explicit live request with your key, and inspect status, latency, size, and exact JSON.

US

Priority county coverage

Share the county FIPS, sample parcel IDs or coordinates, required fields, volume, and target response shape. We will scope the configuration path.

Email coverage request
JSON

Custom response contracts

Bring your existing schema. Enterprise integrations can receive a route shaped around the fields and nesting your product already expects.

Send desired payload
SOS

Production support

For integration blockers, key rotation, data questions, or incident follow-up, contact the PropData team directly.

sales@proptechusa.ai
§

Terms, acceptable use & compliance

Review the complete API terms, security duties, source limitations, regulated-use restrictions, caching rules, and legal notices in one printable policy center.

CURRENT · v1.0

This is the first published API-only terms version in this workspace. No earlier version is represented as available. Future verified revisions will appear here with their effective dates and a real change summary.