Property records from many jurisdictions, one schema.

Sample response

One parcel, one schema.

Universal fields are always present. Jurisdiction-specific fields stay on the object: a value when the market publishes them, null and field_available: false when they do not.

{
  "parcel_id": "us-ct:09-123-456",
  "jurisdiction": "us-ct",
  "geometry": {
    "type": "Polygon",
    "coordinates": [
      [
        [
          -72.673,
          41.765
        ],
        [
          -72.671,
          41.765
        ],
        [
          -72.671,
          41.763
        ],
        [
          -72.673,
          41.763
        ],
        [
          -72.673,
          41.765
        ]
      ]
    ]
  },
  "lot_size_sqft": 8712,
  "building_area_sqft": 1840,
  "year_built": 1924,
  "stories": 2,
  "land_use": "single_family",
  "assessed_value_usd": 287400,
  "bedrooms": 3,
  "bathrooms": 1.5,
  "roof": null,
  "heating": "gas",
  "basement": true,
  "condition": "average",
  "grade": null,
  "field_available": {
    "parcel_geometry": true,
    "lot_size": true,
    "building_area": true,
    "year_built": true,
    "stories": true,
    "land_use": true,
    "assessed_value": true,
    "bedrooms": true,
    "bathrooms": true,
    "roof": false,
    "heating": true,
    "basement": true,
    "condition": true,
    "grade": false
  }
}

{
  "parcel_id": "us-mt:41-98-00421",
  "jurisdiction": "us-mt",
  "geometry": {
    "type": "Polygon",
    "coordinates": [
      [
        [
          -111.042,
          45.678
        ],
        [
          -111.04,
          45.678
        ],
        [
          -111.04,
          45.676
        ],
        [
          -111.042,
          45.676
        ],
        [
          -111.042,
          45.678
        ]
      ]
    ]
  },
  "lot_size_sqft": 43560,
  "building_area_sqft": 2100,
  "year_built": 1978,
  "stories": 1,
  "land_use": "single_family",
  "assessed_value_usd": 312000,
  "bedrooms": null,
  "bathrooms": null,
  "roof": null,
  "heating": null,
  "basement": null,
  "condition": null,
  "grade": null,
  "field_available": {
    "parcel_geometry": true,
    "lot_size": true,
    "building_area": true,
    "year_built": true,
    "stories": true,
    "land_use": true,
    "assessed_value": true,
    "bedrooms": false,
    "bathrooms": false,
    "roof": false,
    "heating": false,
    "basement": false,
    "condition": false,
    "grade": false
  }
}

Who it's for

Teams that need assessor truth in product code.

Same schema whether you score collaterals, map parcels, or ship proptech features — coverage stays honest.

• AVM & valuation models

  Assessor attributes and parcel geometry for model features — not listing prices.

  Learn more→

• Lending & underwriting

  Collateral context from assessor rolls and cadastres, with honest nulls.

  Learn more→

• Insurance & risk

  Parcel and structure attributes for exposure and risk workflows.

  Learn more→

• GIS & mapping

  Parcel polygons plus attributes in one API-shaped response.

  Learn more→

• Proptech products

  Ship product features on government property records without pretending nationwide coverage.

  Learn more→

FAQ

Straight answers before you integrate.

Coverage, licensing, and refresh are per market — not nationwide promises. If something is thin or restricted, we say so.

Why isn't every US county here?+–

Because nationwide coverage is county-by-county licensing and joins — not a single file we can pretend exists. The coverage table is the product surface. If a market is missing, use the form and we will tell you whether we can add it.

Do you skip-trace or sell owner phone numbers?+–

No. Owner names and mailing addresses appear only where the assessor or cadastre publishes them. We do not append mobile numbers, emails, or credit headers.

One schema — what happens when a county has no bedrooms?+–

The field stays on the object. The value is null and field_available is false for that field. You write one parser — no special cases for Connecticut vs Virginia vs the Netherlands. The sample response is the contract.

Can I redistribute this, or put it in a product my customers see?+–

It depends on the market. Licence status is on every coverage row: open, attribution required, licensed, or restricted. Your API terms will spell out in-product use vs reselling a competing dataset. A public GIS download is not automatically a bulk-resale grant — see Data Sources for each publisher.

How far back does history go?+–

This is a current assessor / cadastre snapshot, plus whatever prior assessment years that source publishes. Often one roll, sometimes several. It is not a title plant or deed history. If you need recorded documents or chain of title, say so on the form.

What do you guarantee on refresh?+–

Cadence is per market — see the Refresh column. We ingest after the source posts an update. If a county publishes annually, we are annual. There is no SLA that this matches an unpublished local edit.

Fields

What every record includes — and what varies by market.

Click a field to filter coverage to markets that publish it.

Pricing

Usage-based, per market.

Tell us your markets for a quote — we price by the jurisdictions you need, not a one-size plan.