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 /v1/records/{id}. Share of records with each field:
| Field | Coverage | Share |
|---|---|---|
| Situs address | Most · 79% | |
| Owner name | Nearly all · 99% | |
| Assessed or market value | Nearly all · 99% | |
| Year built | Many · 46% | |
| Building size | Nearly all · 99% | |
| Last sale | Nearly all · 99% | |
| Land use | Nearly all · 99% | |
| Zoning | Not 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 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.
Within 50 km: /v1/lookup section power; details: /v1/records/{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 an address or point: /v1/lookup section utilities
Data-center projects
2 tracked projects: 1 proposed, 1 status not reported.
Within 10 km: /v1/lookup section datacenters
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%.
At an address or point: /v1/lookup section environment
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: /v1/lookup section logistics
Example requests for St. Louis 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 its water and sewer service
/v1/lookup matches 7556 Metske Road, EVELETH, MN and returns the parcel's korzy_id and record, plus the water and sewer service areas at the parcel and the nearest treatment plants. 2 credits.
curl --fail-with-body -sS \
-H "Authorization: Bearer $KORZY_API_KEY" \
-H "Content-Type: application/json" \
-d '{"address":"7556 Metske Road, EVELETH, MN","sections":["utilities"]}' \
https://api.korzy.co/v1/lookupPython
import os
import requests
response = requests.post(
"https://api.korzy.co/v1/lookup",
json={"address": "7556 Metske Road, EVELETH, MN", "sections": ["utilities"]},
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"]["utilities"]["status"])Production response (trimmed)
{
"location": {
"longitude": -92.47921085012382,
"latitude": 47.2972616,
"address": "7556 Metske Road, EVELETH",
"match_type": "exact"
},
"parcels": {
"records": [
{
"id": "27137-c05f9186f1109d5cffc6",
"korzy_id": "27137-c05f9186f1109d5cffc6",
"parcelid": "690-0010-05530",
"parceladdr": "7556 Metske Road",
"parcelcity": "EVELETH",
"situs_zip": "55734",
"statefp": "27",
"geoid": "27137",
"longitude": -92.47921085012382,
"latitude": 47.2972616,
"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"
}
],
"truncated": false
},
"sections": {
"utilities": {
"status": "ok",
"data": {
"treatment_plants": [
{
"id": "utility:treatment:7119",
"feature_id": "treatment:7119",
"name": "IRON JUNCTION WWTP",
"distance_km": 16.64312176287255
},
{
"id": "utility:treatment:7122",
"feature_id": "treatment:7122",
"name": "EVELETH WWTF",
"distance_km": 18.83588754063017
},
{
"id": "utility:treatment:135",
"feature_id": "treatment:135",
"name": "GILBERT WWTP",
"distance_km": 21.56296963305985
}
],
"truncated": {
"water": false,
"sewer": false
}
},
"provenance": [
{
"dataset": "water",
"data_version": "63b7c1c3-9661-4fed-a59f-ddbfff80c2e4"
},
{
"dataset": "sewer",
"data_version": "63b7c1c3-9661-4fed-a59f-ddbfff80c2e4"
},
{
"dataset": "treatment",
"data_version": "63b7c1c3-9661-4fed-a59f-ddbfff80c2e4"
}
]
}
},
"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 27137-c05f9186f1109d5cffc6, 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":"27137-c05f9186f1109d5cffc6"}],"fields":["identity","sale","owner"]}' \
https://api.korzy.co/v1/enrich3. 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/27137-c05f9186f1109d5cffc6JavaScript
const response = await fetch(`https://api.korzy.co/v1/records/${encodeURIComponent("27137-c05f9186f1109d5cffc6")}`, {
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);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. 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 St. Louis County?
- Korzy tracks 2 data-center projects in St. Louis County: 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 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%. A /v1/lookup with the utilities section returns the water and sewer matches at an address or point.
More featured counties
- Hennepin County, MNabout 450,000 parcels
- Dakota County, MNabout 170,000 parcels
- Ramsey County, MNabout 170,000 parcels
- Anoka County, MNabout 150,000 parcels
- Washington County, MNabout 130,000 parcels
Build on St. Louis 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.