Yellowstone County, MT parcel and infrastructure data API

Korzy has about 83,000 parcel records for Yellowstone County, Montana, with source updates through November 2026. Nearly every record carries owner names, values and land use; 87% include last sale and 68% include year built. In and around the county the API also maps 6 data-center projects (4 operating); 6 power plants with about 360 MW of capacity, led by natural gas; and about 210 miles of active rail. Look up any parcel by address or coordinates, then check nearby data-center projects, utilities and grid context at the same point.

Parcel coverage in Yellowstone County

About 83,000 parcel records with boundaries, situs addresses and parcel numbers, with the latest source update from November 2026. Each record has a stable korzy_id you can store and look up again with /v1/records/{id}. Share of records with each field:

FieldCoverageShare
Situs addressNearly all · 99%
Owner nameNearly all · 99%
Assessed or market valueNearly all · 99%
Year builtMany · 68%
Building sizeMany · 68%
Last saleMost · 87%
Land useNearly all · 99%
ZoningNot published

Owner name and mailing address are returned by /v1/enrich with the owner group, at 2 credits per parcel instead of 1 credit. 99% of Yellowstone County records carry an owner name.

Infrastructure in and around Yellowstone County

Power plants

6 operable plants with about 360 MW of nameplate capacity; largest by capacity: natural gas, solar, oil. Proposed generators add about 50 MW.

Within 50 km: /v1/lookup section power; details: /v1/records/{id}

Substations and transmission

About 75 in-service substations, 9 rated 230 kV or higher.

About 630 miles of transmission lines: about 140 mi at under 100 kV; about 210 mi at 100–161 kV; about 150 mi at 220–287 kV; about 130 mi at 500 kV.

Water and sewer service

Service areas of about 30 community water systems cover about 3% of the county.

Sewer service areas of 4 systems cover about 4%.

At an address or point: /v1/lookup section utilities

Data-center projects

6 tracked projects: 4 operating, 1 proposed, 1 status not reported. Reported planned capacity: about 1,000 MW.

Within 10 km: /v1/lookup section datacenters

Flood zones and wetlands

Special flood hazard areas cover about 2% of the county on the current federal flood maps, published September 2026.

Mapped wetlands cover about 1%.

At an address or point: /v1/lookup section environment

Rail, ports and freight

  • About 210 miles of active rail, about 160 of it main line
  • About 95 miles of national freight network highway

Within 25 km: /v1/lookup section logistics

Example requests for Yellowstone County

The lookup response is a real production response, trimmed to the main fields. Every request needs an API key with api:read; see authentication and credits and limits.

1. Find a parcel and nearby data-center projects

/v1/lookup matches 2020 LA BREA ST, BILLINGS, MT and returns the parcel's korzy_id and record, plus the data-center projects within 10 km, nearest first. 2 credits.

curl --fail-with-body -sS \
  -H "Authorization: Bearer $KORZY_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"address":"2020 LA BREA ST, BILLINGS, MT","sections":["datacenters"]}' \
  https://api.korzy.co/v1/lookup
Python
import os
import requests

response = requests.post(
    "https://api.korzy.co/v1/lookup",
    json={"address": "2020 LA BREA ST, BILLINGS, MT", "sections": ["datacenters"]},
    headers={"Authorization": f"Bearer {os.environ['KORZY_API_KEY']}"},
    timeout=60,
)
response.raise_for_status()
body = response.json()
parcel = body["parcels"]["records"][0]
print(parcel["korzy_id"], body["sections"]["datacenters"]["status"])
Production response (trimmed)
{
  "location": {
    "longitude": -108.55029880075759,
    "latitude": 45.79083935,
    "address": "2020 LA BREA ST, BILLINGS",
    "match_type": "exact"
  },
  "parcels": {
    "records": [
      {
        "id": "30111-f9264911eae5e7f46cc0",
        "korzy_id": "30111-f9264911eae5e7f46cc0",
        "parcelid": "03103236425050000",
        "parceladdr": "2020 LA BREA ST",
        "parcelcity": "BILLINGS",
        "situs_zip": "59102",
        "statefp": "30",
        "geoid": "30111",
        "longitude": -108.55029880075759,
        "latitude": 45.79083935,
        "usedesc": "Exempt Property",
        "yearbuilt": 1959,
        "bldgsqft": 1278,
        "taxacres": 0.172167413589954,
        "totalvalue": 379900,
        "land_value_usd": 47988,
        "improvement_value_usd": 331912,
        "saledate": "2018-11-15",
        "updated": "2026-11-03"
      }
    ],
    "truncated": false
  },
  "sections": {
    "datacenters": {
      "status": "ok",
      "data": {
        "radius_km": 10,
        "projects": [
          {
            "id": "datacenter:dc_834a609c7f22fc5a87c0",
            "project_id": "dc_834a609c7f22fc5a87c0",
            "name": "Vision Net Billings 2 (1030 Central Avenue)",
            "operator": "Vision Net",
            "status": "operating",
            "state": "MT",
            "city": "Billings",
            "address": "1030 Central Ave",
            "longitude": -108.542169482237,
            "latitude": 45.76973999352,
            "location_precision": "approximate",
            "source_count": 1,
            "source_date": "2026-10-08",
            "mapped": true,
            "distance_km": 2.4293666031892442
          },
          {
            "id": "datacenter:dc_36d56f0a84fe352bc00f",
            "project_id": "dc_36d56f0a84fe352bc00f",
            "name": "Vision Net Billings Fiber Hotel (Granite Tower, formerly iConnect Billings)",
            "operator": "Vision Net",
            "status": "operating",
            "state": "MT",
            "city": "Billings",
            "address": "222 N 32nd St",
            "longitude": -108.512522,
            "latitude": 45.781098,
            "location_precision": "approximate",
            "source_count": 1,
            "source_date": "2026-10-08",
            "mapped": true,
            "distance_km": 3.123103950489095
          },
          {
            "id": "datacenter:dc_997fc1021f03a3936f51",
            "project_id": "dc_997fc1021f03a3936f51",
            "name": "Cogent Billings Data Center",
            "operator": "Cogent Communications",
            "status": "operating",
            "state": "MT",
            "city": "Billings",
            "address": "3025 Hesper Rd",
            "longitude": -108.591913,
            "latitude": 45.740895,
            "location_precision": "approximate",
            "source_count": 1,
            "source_date": "2026-10-08",
            "mapped": true,
            "distance_km": 6.423538140040669
          }
        ],
        "truncated": false,
        "note": "Straight-line distance to the reported project point; inspect location_precision. Projects merge supported source matches, not every nearby building. Approximate locations do not identify a parcel. Reported IT load, facility power, planned capacity and estimates remain separate source claims. No record or unknown status does not establish absence or inactivity."
      },
      "provenance": [
        {
          "dataset": "datacenters",
          "as_of": "2026-11-02",
          "data_version": "20261102T123021962884Z"
        }
      ]
    }
  },
  "credits": {
    "charged": 2,
    "refunded": 0
  }
}

2. Add owner and sale fields

/v1/enrich returns the fields you choose for up to 25 parcels per request; here the parcel 30111-f9264911eae5e7f46cc0, with the owner group. 2 credits.

curl --fail-with-body -sS \
  -H "Authorization: Bearer $KORZY_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"items":[{"korzy_id":"30111-f9264911eae5e7f46cc0"}],"fields":["identity","sale","owner"]}' \
  https://api.korzy.co/v1/enrich

3. Fetch the record again by ID

/v1/records/{id} returns the stored parcel's full record, without owner fields. 1 credit.

curl --fail-with-body -sS \
  -H "Authorization: Bearer $KORZY_API_KEY" \
  https://api.korzy.co/v1/records/30111-f9264911eae5e7f46cc0
JavaScript
const response = await fetch(`https://api.korzy.co/v1/records/${encodeURIComponent("30111-f9264911eae5e7f46cc0")}`, {
  headers: { Authorization: `Bearer ${process.env.KORZY_API_KEY}` },
});
if (!response.ok) throw new Error(`Korzy API ${response.status}`);
const { record } = await response.json();
console.log(record.parceladdr, record.usedesc);

Yellowstone County data questions

How many parcels in Yellowstone County include year built?
About 56,000 of about 83,000 parcel records (68%) include year built.
Does the Korzy API return owner names for Yellowstone County parcels?
Yes. 99% of Yellowstone County parcel records carry an owner name. Ask /v1/enrich for the owner group; each parcel then costs 2 credits instead of 1 credit. Lookups and records never include owner fields.
How many data-center projects are in Yellowstone County?
Korzy tracks 6 data-center projects in Yellowstone County: 4 operating, 1 proposed and 1 status not reported. A /v1/lookup with the datacenters section lists projects within 10 km of any address or point.
How much power generation is in Yellowstone County?
6 operable power plants in Yellowstone County total about 360 MW of nameplate capacity, mainly natural gas, solar and oil.
Which water systems serve Yellowstone County?
Service areas of about 30 community water systems cover about 3% of Yellowstone County, and sewer service areas cover about 4%. A /v1/lookup with the utilities section returns the water and sewer matches at an address or point.

Build on Yellowstone County parcel data

Lookups, enrichment and records work the same in every county Korzy covers. Credits are shared across parcels, utilities, environment, logistics, power, grid, data-center and terrain sections.