Baltimore city, MD parcel and infrastructure data API
Korzy has about 240,000 parcel records for Baltimore city, Maryland, with source updates through July 2026. Nearly every record carries land use, year built and building size; 69% include last sale. In and around the county the API also maps 8 data-center projects (5 operating); 1 port with reported cargo; and about 10 power plants with about 180 MW of capacity, led by oil. 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 Baltimore city
About 240,000 parcel records with boundaries, situs addresses and parcel numbers, with the latest source update from July 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 · 100% | |
| Owner name | Not published | |
| Assessed or market value | Some · 7% | |
| Year built | Nearly all · 98% | |
| Building size | Nearly all · 97% | |
| Last sale | Many · 69% | |
| Land use | Nearly all · 98% | |
| Zoning | Not published |
Baltimore city records do not include owner names. See pricing for credit costs.
Infrastructure in and around Baltimore city
Power plants
About 10 operable plants with about 180 MW of nameplate capacity; largest by capacity: oil, other fuels, natural gas.
Plant details: /api/power/plants/{plant_id}
Substations and transmission
About 30 in-service substations, 1 rated 230 kV or higher.
About 45 miles of transmission lines: about 40 mi at 100–161 kV; 3 mi at 220–287 kV.
Water and sewer service
Service areas of 5 community water systems cover about 94% of the county.
Sewer service areas of 3 systems cover about 94%.
At a point: /api/utilities/context
Data-center projects
8 tracked projects: 5 operating, 3 status not reported. Reported operating capacity: about 85 MW.
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 May 2026.
Mapped wetlands cover about 1%.
Rail, ports and freight
- About 120 miles of active rail, about 45 of it main line
- About 50 miles of national freight network highway
- 1 port area with reported cargo tonnage
- 2 intermodal rail terminals
Within 25 km of a point: /api/logistics/context
Example requests for Baltimore city
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 707 E 34TH ST, BALTIMORE, MD 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=707 E 34TH ST, BALTIMORE, MD' \
https://api.korzy.co/api/searchPython
import os
import requests
response = requests.get(
"https://api.korzy.co/api/search",
params={"q": "707 E 34TH ST, BALTIMORE, MD"},
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": "24510-94c12cf3092c8ecdf9c3",
"address": "707 E 34TH ST",
"city": "BALTIMORE",
"postcode": "21218",
"county": "Baltimore",
"statefp": "24",
"longitude": -76.60584942562795,
"latitude": 39.32937825,
"match_type": "exact",
"parcelid": "4053076",
"parceladdr": "707 E 34TH ST",
"parcelcity": "BALTIMORE",
"situs_zip": "21218",
"usedesc": "SCHOOL #115 ",
"yearbuilt": 1959,
"bldgsqft": 30036,
"totalvalue": 2194800,
"updated": "2026-07-13",
"geoid": "24510"
}
],
"truncated": false
}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, 24510-94c12cf3092c8ecdf9c3, in records. 1 credit per 10 records requested.
curl --fail-with-body -sS --get \
-H "Authorization: Bearer $KORZY_API_KEY" \
--data-urlencode 'longitude=-76.605849' \
--data-urlencode 'latitude=39.329378' \
--data-urlencode 'limit=5' \
https://api.korzy.co/api/query/pointJavaScript
const params = new URLSearchParams({"longitude": "-76.605849", "latitude": "39.329378", "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=-76.605849' \
--data-urlencode 'latitude=39.329378' \
--data-urlencode 'radius_km=10' \
--data-urlencode 'limit=3' \
https://api.korzy.co/api/datacenters/contextPython
import os
import requests
response = requests.get(
"https://api.korzy.co/api/datacenters/context",
params={"longitude": "-76.605849", "latitude": "39.329378", "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_fcc6360dd42cdc9b948b",
"name": "DataBank BWI1 (Downtown Baltimore Data Center)",
"operator": "DataBank",
"status": "operating",
"city": "Baltimore",
"state": "MD",
"longitude": -76.619738877727,
"latitude": 39.291652966378,
"location_precision": "exact",
"operational_mw": 1.5,
"distance_km": 4.3617319821373925
},
{
"project_id": "dc_3776ed3467998cde6a02",
"name": "AiNET One Market Center (Baltimore Carrier Hotel)",
"operator": "AiNET",
"status": "operating",
"city": "Baltimore",
"state": "MD",
"longitude": -76.6203737,
"latitude": 39.2917583,
"location_precision": "exact",
"operational_mw": 80,
"distance_km": 4.365786636134418
},
{
"project_id": "dc_2375c35dce2ddcdc13bd",
"name": "Lumen Baltimore 1",
"operator": "Lumen Technologies",
"status": "operating",
"city": "Baltimore",
"state": "MD",
"longitude": -76.6204024,
"latitude": 39.2917592,
"location_precision": "exact",
"distance_km": 4.366398157230365
}
],
"radius_km": 10,
"limit": 3,
"truncated": true
}Baltimore city data questions
- How many parcels in Baltimore city include year built?
- About 240,000 of about 240,000 parcel records (98%) include year built.
- Does the Korzy API return owner names for Baltimore city parcels?
- Baltimore city parcel records do not include owner names. Values, land use and building facts are returned where the county publishes them.
- How many data-center projects are in Baltimore city?
- Korzy tracks 8 data-center projects in Baltimore city: 5 operating and 3 status not reported. /api/datacenters/context lists projects within 10 km of any point.
- How much power generation is in Baltimore city?
- About 10 operable power plants in Baltimore city total about 180 MW of nameplate capacity, mainly oil, other fuels and natural gas.
- Which water systems serve Baltimore city?
- Service areas of 5 community water systems cover about 94% of Baltimore city, and sewer service areas cover about 94%. /api/utilities/context returns the water and sewer matches at a point.
More featured counties
- Baltimore County, MDBorders Baltimore city · about 370,000 parcels
- Prince George's County, MDabout 350,000 parcels
- Frederick County, MDabout 120,000 parcels
- Montgomery County, MDabout 290,000 parcels
Build on Baltimore city 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.