Property records from many jurisdictions, one schema.

Assessors, GIS shops, and cadastres all publish parcels — none share a format. PlatMint normalizes them into one JSON shape. When a market does not publish a field, you get null and field_available: false.

141,627,506
parcels across covered markets
33
jurisdictions
1
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.

GET https://api.platmint.com/v1/parcels?address=123%20Main%20St,%20Hartford,%20CT
Authorization: Bearer pt_live_••••••••

bedrooms is 3. field_available.bedrooms is true.

{
  "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
  }
}

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.

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.

On every market

Always in the schema, populated from the source.

Jurisdiction-specific

Same keys everywhere. Null + field_available: false when missing.

Coverage

Markets we cover today.

33 jurisdictions. Licence and refresh are per row — check before you build.

Showing markets with Year built.

33 markets

  • Connecticutbeds+baths

    US statewide · Open · annual

    Statewide parcel + CAMA join. Canaan has geometry without CAMA.

    12 fields in schema

  • Massachusettsbeds+baths

    US statewide · Attribution · annual

    MassGIS standardized parcels; CAMA completeness varies by town.

    12 fields in schema

  • Rhode Islandbeds+baths

    US statewide · Open · annual

    RIGIS statewide parcels with municipal assessor attributes.

    11 fields in schema

  • US statewide · Open · annual

    VCGI grand list parcels. Beds/baths are not in the statewide join.

    8 fields in schema

  • Mainebeds+baths

    US statewide · Attribution · annual

    Municipal parcel mosaic. Attribute depth follows town CAMA.

    9 fields in schema

  • New Hampshirebeds+baths

    US statewide · Attribution · annual

    GRANIT / municipal mosaic. Not every town publishes beds.

    9 fields in schema

  • New Yorkbeds+baths

    US statewide · Attribution · annual

    NYS GIS tax parcels. NYC is also listed as its own county-level row.

    13 fields in schema

  • New Jerseybeds+baths

    US statewide · Attribution · annual

    MOD-IV / statewide parcels. Building fields follow municipal CAMA.

    11 fields in schema

  • Marylandbeds+baths

    US statewide · Attribution · annual

    SDAT / MDP statewide property view.

    12 fields in schema

  • Delawarebeds+baths

    US statewide · Open · annual

    FirstMap statewide parcels.

    9 fields in schema

  • US statewide · Attribution · annual

    VGIN statewide parcels. Building characteristics are local, not in the state layer.

    7 fields in schema

  • US statewide · Attribution · annual

    NC OneMap parcels. Assessor fields are county-by-county.

    7 fields in schema

  • US statewide · Attribution · annual

    Statewide parcel geometry; CAMA join is incomplete.

    7 fields in schema

  • US statewide · Attribution · quarterly

    Statewide tax-roll parcels. Beds/baths are not on the statewide schema.

    7 fields in schema

  • US statewide · Open · annual

    Cadastral parcels. Building area / year built sparse outside cities.

    7 fields in schema

  • US statewide · Open · annual

    AGRC statewide parcels.

    7 fields in schema

  • US statewide · Attribution · annual

    GEO / county mosaic. Building fields are not statewide.

    7 fields in schema

  • US statewide · Attribution · annual

    Statewide parcel fabric. King County is listed separately with richer CAMA.

    7 fields in schema

  • US statewide · Attribution · annual

    IGIC / county parcel mosaic.

    7 fields in schema

  • US statewide · Attribution · annual

    MnGeo parcels. Metro counties publish more CAMA than Greater Minnesota.

    7 fields in schema

  • Cook County, ILbeds+baths

    US county · Attribution · annual

    Assessor CAMA + parcel polygons.

    12 fields in schema

  • US county · Attribution · weekly

    Assessor portal extracts. Licence is attribution, not a bulk resale grant.

    11 fields in schema

  • US county · Open · weekly

    HCAD public extracts.

    10 fields in schema

  • King County, WAbeds+baths

    US county · Open · weekly

    Open data CAMA is among the richest county extracts we ship.

    13 fields in schema

  • US county · Attribution · monthly

    County GIS + property appraiser. Statewide FL row does not include beds.

    10 fields in schema

  • US county · Open · weekly

    Assessor open data.

    10 fields in schema

  • US county · Attribution · monthly

    PLUTO / MapPLUTO. Tax lots, not a full CAMA beds file for every class.

    13 fields in schema

  • US county · Attribution · annual

    County GIS parcels with residential CAMA on improved lots.

    9 fields in schema

  • International · Attribution · quarterly

    INSPIRE index polygons. This is cadastral geometry, not UK Energy Performance beds.

    7 fields in schema

  • International · Attribution · monthly

    BAG / PDOK. Dwellings, not US-style bedroom counts.

    8 fields in schema

  • International · Attribution · monthly

    LINZ NZ Parcels. Building attributes are a separate layer.

    7 fields in schema

  • International · Attribution · annual

    Tailte Éireann / OSI cadastral parcels.

    7 fields in schema

  • International · Open · annual

    PCI / cadastre Etalab. Parcels, not logements.

    7 fields in schema

Not seeing your market? Tell us.

Pricing

Usage-based, per market.

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

Need a market we list — or one we do not?

Share your email and markets. If we already cover one, you get its field list with the reply.

Get access

Access

Request access for the markets you need.

Tell us your email, markets, and what you’re building. If a selected market is already covered, you get its field list on submit. Either way, we reply within one business day.

Step 1 of 2

Markets

Not in the list? Keep typing and add it anyway.