St. Louis County, MN parcel and infrastructure data API

Korzy has about 190,000 parcel records for St. Louis County, Minnesota, with source updates through November 2026. Nearly every record carries owner names, values, last sale, land use and building size; 46% include year built. In and around the county the API also maps about 580 miles of active rail; 2 data-center projects; and 1 port with reported cargo. Look up any parcel by address or coordinates, then check water, sewer and infrastructure context at the same point.

Parcel coverage in St. Louis County

About 190,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:

FieldCoverageShare
Situs addressMost · 79%
Owner nameNearly all · 99%
Assessed or market valueNearly all · 99%
Year builtMany · 46%
Building sizeNearly all · 99%
Last saleNearly all · 99%
Land useNearly all · 99%
ZoningNot 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 St. Louis County records carry an owner name.

Infrastructure in and around St. Louis County

Power plants

7 operable plants with about 270 MW of nameplate capacity; largest by capacity: natural gas, other fuels, wind.

Plant details: /api/power/plants/{plant_id}

Substations and transmission

About 140 in-service substations, 6 rated 230 kV or higher.

About 1,100 miles of transmission lines: about 130 mi at under 100 kV; about 620 mi at 100–161 kV; about 180 mi at 220–287 kV; about 10 mi at 345 kV; about 75 mi at 500 kV.

Water and sewer service

Service areas of about 35 community water systems cover about 1% of the county.

Sewer service areas of about 20 systems cover about 3%.

At a point: /api/utilities/context

Data-center projects

2 tracked projects: 1 proposed, 1 status not reported.

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

Flood zones and wetlands

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

Mapped wetlands cover about 30%.

Rail, ports and freight

  • About 580 miles of active rail, about 430 of it main line
  • About 15 miles of national freight network highway
  • 1 port area with reported cargo tonnage
  • 1 intermodal rail terminal

Within 25 km of a point: /api/logistics/context

Example requests for St. Louis 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 7556 Metske Road, EVELETH, MN 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=7556 Metske Road, EVELETH, MN' \
  https://api.korzy.co/api/search
Python
import os
import requests

response = requests.get(
    "https://api.korzy.co/api/search",
    params={"q": "7556 Metske Road, EVELETH, MN"},
    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": "27137-c05f9186f1109d5cffc6",
      "address": "7556 Metske Road",
      "city": "EVELETH",
      "postcode": "55734",
      "county": "ST. LOUIS",
      "statefp": "27",
      "longitude": -92.47921085012382,
      "latitude": 47.2972616,
      "match_type": "exact",
      "parcelid": "690-0010-05530",
      "parceladdr": "7556 Metske Road",
      "parcelcity": "EVELETH",
      "situs_zip": "55734",
      "usedesc": "Commercial Preferred",
      "yearbuilt": 1977,
      "taxacres": 24.82,
      "land_value_usd": 72700,
      "improvement_value_usd": 165000,
      "market_value_usd": 237700,
      "saledate": "2015-02-10",
      "saleamt": 168000,
      "updated": "2026-11-03",
      "geoid": "27137"
    }
  ],
  "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, 27137-c05f9186f1109d5cffc6, in records. 1 credit per 10 records requested.

curl --fail-with-body -sS --get \
  -H "Authorization: Bearer $KORZY_API_KEY" \
  --data-urlencode 'longitude=-92.479211' \
  --data-urlencode 'latitude=47.297262' \
  --data-urlencode 'limit=5' \
  https://api.korzy.co/api/query/point
JavaScript
const params = new URLSearchParams({"longitude": "-92.479211", "latitude": "47.297262", "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 water and sewer service

/api/utilities/context returns the water and sewer service areas at the point and the nearest treatment plants. 1 credit.

curl --fail-with-body -sS --get \
  -H "Authorization: Bearer $KORZY_API_KEY" \
  --data-urlencode 'longitude=-92.479211' \
  --data-urlencode 'latitude=47.297262' \
  https://api.korzy.co/api/utilities/context
Python
import os
import requests

response = requests.get(
    "https://api.korzy.co/api/utilities/context",
    params={"longitude": "-92.479211", "latitude": "47.297262"},
    headers={"Authorization": f"Bearer {os.environ['KORZY_API_KEY']}"},
    timeout=30,
)
response.raise_for_status()
matches = response.json()["matches"]
print([area["name"] for area in matches["water"]])
Response (trimmed)
{
  "longitude": -92.479211,
  "latitude": 47.297262,
  "matches": {
    "water": [],
    "sewer": []
  },
  "nearby_treatment": [
    {
      "feature_id": "treatment:7119",
      "name": "IRON JUNCTION WWTP",
      "distance_km": 16.64307891972354
    },
    {
      "feature_id": "treatment:7122",
      "name": "EVELETH WWTF",
      "distance_km": 18.835841654610807
    }
  ]
}

St. Louis County data questions

How many parcels in St. Louis County include year built?
About 87,000 of about 190,000 parcel records (46%) include year built.
Does the Korzy API return owner names for St. Louis County parcels?
Yes. 99% of St. Louis 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 St. Louis County?
Korzy tracks 2 data-center projects in St. Louis County: 1 proposed and 1 status not reported. /api/datacenters/context lists projects within 10 km of any point.
How much power generation is in St. Louis County?
7 operable power plants in St. Louis County total about 270 MW of nameplate capacity, mainly natural gas, other fuels and wind.
Which water systems serve St. Louis County?
Service areas of about 35 community water systems cover about 1% of St. Louis County, and sewer service areas cover about 3%. /api/utilities/context returns the water and sewer matches at a point.

More featured counties

All featured Minnesota counties

Build on St. Louis 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.