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. Add include_owner=true to a point, search or parcel-record request; it doubles the request's cost, so a single parcel record costs 2 credits.

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. /api/datacenters/context lists projects within 10 km of any 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%. /api/utilities/context returns the water and sewer matches at a point.

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.

Get an API key Read the API docs

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 /api/parcel-record. Share of records with each field:

Field	Coverage	Share
Situs address	Nearly all · 99%
Owner name	Nearly all · 99%
Assessed or market value	Nearly all · 99%
Year built	Many · 68%
Building size	Many · 68%
Last sale	Most · 87%
Land use	Nearly all · 99%
Zoning	Not published

Owner name and mailing address are returned with include_owner=true, which doubles a request's cost: a parcel record costs 2 credits instead of 1. 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.

Plant details: /api/power/plants/{plant_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 a point: /api/utilities/context

Data-center projects

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

Within 10 km of a point: /api/datacenters/context

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%.

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 of a point: /api/logistics/context

Example requests for Yellowstone County

Real responses from the production API, trimmed to the main fields. Every request needs an API key with api:read; see authentication and credits and limits.

1. Find a parcel by address

/api/search matches 2020 LA BREA ST, BILLINGS, MT and returns the parcel's korzy_id, coordinates and record. 1 credit.

curl --fail-with-body -sS --get \
  -H "Authorization: Bearer $KORZY_API_KEY" \
  --data-urlencode 'q=2020 LA BREA ST, BILLINGS, MT' \
  https://api.korzy.co/api/search

Python

import os
import requests

response = requests.get(
    "https://api.korzy.co/api/search",
    params={"q": "2020 LA BREA ST, BILLINGS, MT"},
    headers={"Authorization": f"Bearer {os.environ['KORZY_API_KEY']}"},
    timeout=30,
)
response.raise_for_status()
parcel = response.json()["results"][0]
print(parcel["korzy_id"], parcel["longitude"], parcel["latitude"])

Response (trimmed)

{
  "results": [
    {
      "korzy_id": "30111-f9264911eae5e7f46cc0",
      "address": "2020 LA BREA ST",
      "city": "BILLINGS",
      "postcode": "59102",
      "county": "Yellowstone",
      "statefp": "30",
      "longitude": -108.55029880075759,
      "latitude": 45.79083935,
      "match_type": "exact",
      "parcelid": "03103236425050000",
      "parceladdr": "2020 LA BREA ST",
      "parcelcity": "BILLINGS",
      "situs_zip": "59102",
      "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",
      "geoid": "30111"
    }
  ],
  "truncated": false
}

With include_owner=true (2 credits) the record adds owner fields, shown here as placeholders:

{
  "owner_name": "EXAMPLE HOLDINGS LLC",
  "owner_mailing_address": "100 EXAMPLE ST, SAMPLE CITY, ST 00000"
}

2. Look up the parcel at a point

/api/query/point returns every parcel whose boundary covers the coordinates; here it returns the same record, 30111-f9264911eae5e7f46cc0, in records. 1 credit per 10 records requested.

curl --fail-with-body -sS --get \
  -H "Authorization: Bearer $KORZY_API_KEY" \
  --data-urlencode 'longitude=-108.550299' \
  --data-urlencode 'latitude=45.790839' \
  --data-urlencode 'limit=5' \
  https://api.korzy.co/api/query/point

JavaScript

const params = new URLSearchParams({"longitude": "-108.550299", "latitude": "45.790839", "limit": "5"});
const response = await fetch(`https://api.korzy.co/api/query/point?${params}`, {
  headers: { Authorization: `Bearer ${process.env.KORZY_API_KEY}` },
});
if (!response.ok) throw new Error(`Korzy API ${response.status}`);
const { records } = await response.json();
console.log(records.map((record) => record.korzy_id));

3. Check nearby data-center projects

/api/datacenters/context lists data-center projects within 10 km of the point, nearest first. 1 credit per 10 records requested.

curl --fail-with-body -sS --get \
  -H "Authorization: Bearer $KORZY_API_KEY" \
  --data-urlencode 'longitude=-108.550299' \
  --data-urlencode 'latitude=45.790839' \
  --data-urlencode 'radius_km=10' \
  --data-urlencode 'limit=3' \
  https://api.korzy.co/api/datacenters/context

Python

import os
import requests

response = requests.get(
    "https://api.korzy.co/api/datacenters/context",
    params={"longitude": "-108.550299", "latitude": "45.790839", "radius_km": "10", "limit": "3"},
    headers={"Authorization": f"Bearer {os.environ['KORZY_API_KEY']}"},
    timeout=30,
)
response.raise_for_status()
for project in response.json()["projects"]:
    print(project["name"], project["status"], project["distance_km"])

Response (trimmed)

{
  "projects": [
    {
      "project_id": "dc_834a609c7f22fc5a87c0",
      "name": "Vision Net Billings 2 (1030 Central Avenue)",
      "operator": "Vision Net",
      "status": "operating",
      "city": "Billings",
      "state": "MT",
      "longitude": -108.542169482237,
      "latitude": 45.76973999352,
      "location_precision": "approximate",
      "distance_km": 2.4293330282839047
    },
    {
      "project_id": "dc_36d56f0a84fe352bc00f",
      "name": "Vision Net Billings Fiber Hotel (Granite Tower, formerly iConnect Billings)",
      "operator": "Vision Net",
      "status": "operating",
      "city": "Billings",
      "state": "MT",
      "longitude": -108.512522,
      "latitude": 45.781098,
      "location_precision": "approximate",
      "distance_km": 3.123104951759795
    },
    {
      "project_id": "dc_997fc1021f03a3936f51",
      "name": "Cogent Billings Data Center",
      "operator": "Cogent Communications",
      "status": "operating",
      "city": "Billings",
      "state": "MT",
      "longitude": -108.591913,
      "latitude": 45.740895,
      "location_precision": "approximate",
      "distance_km": 6.423496731296088
    }
  ],
  "radius_km": 10,
  "limit": 3,
  "truncated": true
}

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. Add include_owner=true to a point, search or parcel-record request; it doubles the request's cost, so a single parcel record costs 2 credits.
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. /api/datacenters/context lists projects within 10 km of any 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%. /api/utilities/context returns the water and sewer matches at a point.

Build on Yellowstone County parcel data

Search, point and record lookups work the same in every county Korzy covers. Credits are shared across parcels, utilities, environment, logistics and data-center routes.

Get an API key See pricing API reference Use cases for parcel and infrastructure data