191.3M PARCEL IDS · 110.0M MAPPED LOCATIONS
MEASURED 2026-08-30 · 50 STATES + DC
MEASURED 2026-08-30 · 50 STATES + DC
U.S. property data.
Delivered where you work.
Explore owners, values, sales, permits and risk through the app, API and bulk data. Coverage, fields and update dates vary by dataset and delivery channel.
INTERACTIVE DEMO — SIX SAMPLE PARCELSAUTO-TOUR ON · TYPE TO TAKE OVER
ENTER ↵
SAMPLE RECORD
1100 E 6th St
Austin, TX 78702
MIXED-USEABSENTEE OWNER
OWNER
EAST SIXTH YARD LLC
↳ M. Delgado · resolved principal · 14 linked parcels
ESTIMATED VALUE
$11.8M$11.1M – $12.6M
PERMITS12 on record · Alteration · Sep 2025
RISKFlood Mod · Wind Mod · Wildfire Low
FULL RECORD FREE IN THE APPOpen in PropRaven →
67% OF PARCEL IDS HAVE COORDINATES
PARCEL MEASUREMENT · 2026-08-30
COVERAGE VARIES BY COUNTY AND FIELD
CHECK FRESHNESS FOR YOUR DATASET
01 / THE SPINEPARCEL MEASUREMENT · 2026-08-30
191M+
DISTINCT PARCEL IDS · 50 STATES + DC
110M+
MAPPED LOCATIONS
67%
OF PARCEL IDS HAVE COORDINATES
Historical measurement; figures above round down. About 129.0M parcel IDs had coordinates. Multiple IDs can share a mapped location. These are not current database row counts.
CHECK DATA FRESHNESS →02 / FRONT DOORSCHOOSE YOUR DELIVERY FORMAT
Get it the way you already work.
Explore the formats below. Available datasets, fields and release dates differ by channel; confirm the coverage you need before integrating.
09Excel add-inThe spine, in a cell function.SOON
Examples are not live responses. Check the channel documentation for access and dataset availability.
03 / UNDERSTAND THE COVERAGESOURCE · SCOPE · DATES
Know what your data covers.
Property records come from many sources with different update schedules. Use the coverage and freshness details to decide whether a dataset fits your work.
01Check local coverageCounty and field coverage varies. A missing deed, permit or owner field does not establish that no record exists.
02Read the datesA source record date, a dataset build date and a publication date describe different events. Check the freshness information for the dataset you use.
03Compare your deliveryThe app, API and bulk releases can differ in fields and timing. Compare a sample from your chosen channel with the source records before relying on it.
BEFORE YOU RELY ON A DATASET
Choose your areaSCOPE
Start with the states and counties relevant to your work.
Check the fieldsCOVERAGE
Review availability for the owner, sale, permit and risk fields you need.
Check freshnessDATES
Use the dataset's source and publication dates, not the homepage measurement date.
Compare recordsSAMPLE
Check known parcels against county records in the channel you plan to use.
COVERAGE AND FRESHNESS VARY BY DATASET.
A SUCCESSFUL LOOKUP DOES NOT VERIFY EVERY FIELD.
A SUCCESSFUL LOOKUP DOES NOT VERIFY EVERY FIELD.
04 / PRICINGTHE METER IS LOOKUPS — NOTHING ELSE
Start free. Scale when it's working.
FREE
$0
For trying it out
1,000 lookups / mo
Full records in the web app — owner, sales, permits, value & risk
Self-serve API keys
NO CARD REQUIRED
BEST FOR ACTIVE INVESTORS
DEVELOPER
$99/mo
For builders & active investors
100k lookups / mo
Full API, SDKs & webhooks
MCP connector — PropRaven inside Claude & AI agents
Owner & sponsor graph
14-DAY FREE TRIAL · CARD REQUIRED
TEAM
$1,000/mo
For teams & production workloads
1M lookups / mo
Everything in Developer
Bulk export
Priority support
BILLED MONTHLY
DATA LICENSE
Custom
State & national bulk
Full state or national tables
Snowflake · Databricks · S3 (Parquet)
Refreshed on cadence, unmetered
SLA & priority support
ANNUAL LICENSE · INVOICED
05 / FAQSIX QUESTIONS · STRAIGHT ANSWERS
Questions engineers ask first.
- 01What is PropRaven?
- PropRaven brings together U.S. parcel, owner, value, sales, permit and risk data from county records and other public sources. The app, API and bulk datasets support different workflows; their fields, coverage and update dates can differ. See the data →
- 02How many parcels are covered?
- The 2026-08-30 measurement recorded about 191.3M distinct state-and-parcel ID pairs across 50 states and DC, and 110.0M mapped locations. About 129.0M of those IDs had coordinates (67%, rounded down). Multiple IDs can share one mapped location. IDs are not a count of unique physical properties, and these historical figures are not current database row counts. Coverage by state →
- 03Where does the data come from and how often is it refreshed?
- County assessor, recorder and building-permit records are combined with public reference data such as FEMA flood zones and Census tracts. Refresh timing varies by source and dataset. A build or publication date does not mean every underlying record was updated then; check the dataset's freshness details and local coverage. Data freshness →
- 04Is there a free tier?
- Yes. The Free plan is $0: 1,000 lookups a month, full records in the web app — owner, sales, permits, value and risk — and self-serve API keys. No card required and no sales call. Paid plans start at $99 a month for 100k lookups with the full API, SDKs, webhooks and the MCP connector; state and national bulk tables are sold under an annual data license. Start free →
- 05How do I access it (API, MCP server, Snowflake Marketplace, SDKs)?
- Use the web app, REST API or MCP server for property lookups. Developer documentation describes SDKs and events; bulk delivery options include warehouse sharing and Parquet files. Confirm access, available fields and the release date for your chosen channel. The examples on this page illustrate formats and are not live responses or a cross-channel verification. Developer docs →
- 06Can AI agents pay per call?
- Yes. A wallet-bearing agent can buy a per-parcel dossier, lead feed, owner report, comp pack or risk score per call over x402 — USDC on Base, no account required. Request the resource without payment and the HTTP 402 response says exactly what to sign; the exact price is previewed for free before you pay, and a failed build is never charged. Discovering the field catalog and the hosted MCP server is free. Agent docs →
06 / START
Evaluate with your own sample.
Engineers don't take our word for it. Take the data.
01 — LOOK UP
Start with a few properties you know in the app or API.
02 — CHECK COVERAGE
Confirm the fields, source dates and delivery options your workflow needs.
03 — COMPARE
Compare the returned records with your own county sample.