Anchorage Municipality, AK parcel and infrastructure data API
Korzy has about 100,000 parcel records for Anchorage Municipality, Alaska, with source updates through October 2026. Nearly every record carries owner names, values and land use; 94% include last sale and 87% include year built. In and around the municipality the API also maps 3 data-center projects (3 operating); 7 power plants with about 870 MW of capacity, led by natural gas; 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 Anchorage Municipality
About 100,000 parcel records with boundaries, situs addresses and parcel numbers, with the latest source update from October 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 | Nearly all · 99% | |
| Owner name | Nearly all · 99% | |
| Assessed or market value | Nearly all · 99% | |
| Year built | Most · 87% | |
| Building size | Not published | |
| Last sale | Most · 94% | |
| Land use | Nearly all · 99% | |
| Zoning | Nearly all · 99% |
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 Anchorage Municipality records carry an owner name.
Infrastructure in and around Anchorage Municipality
Power plants
7 operable plants with about 870 MW of nameplate capacity; largest by capacity: natural gas, battery and pumped storage, wind.
Within 50 km: /v1/lookup section power; details: /v1/records/{id}
Substations and transmission
About 60 in-service substations, 5 rated 230 kV or higher.
About 200 miles of transmission lines: 8 mi at under 100 kV; about 150 mi at 100–161 kV; about 35 mi at 220–287 kV.
Water and sewer service
Service areas of about 50 community water systems cover about 13% of the municipality.
Sewer service areas of 3 systems cover about 6%.
At an address or point: /v1/lookup section utilities
Data-center projects
3 tracked projects: 3 operating.
Within 10 km: /v1/lookup section datacenters
Flood zones and wetlands
Mapped wetlands cover about 4%.
At an address or point: /v1/lookup section environment
Rail, ports and freight
- About 150 miles of active rail, about 100 of it main line
- About 100 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 Anchorage Municipality
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 2735 E TUDOR RD, Anchorage, AK 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":"2735 E TUDOR RD, Anchorage, AK","sections":["utilities"]}' \
https://api.korzy.co/v1/lookupPython
import os
import requests
response = requests.post(
"https://api.korzy.co/v1/lookup",
json={"address": "2735 E TUDOR RD, Anchorage, AK", "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": -149.82953577511898,
"latitude": 61.18136645,
"address": "2735 E TUDOR RD, Anchorage",
"match_type": "exact"
},
"parcels": {
"records": [
{
"id": "02020-3313f12fb1fe809d838c",
"korzy_id": "02020-3313f12fb1fe809d838c",
"parcelid": "00803207000",
"parceladdr": "2735 E TUDOR RD",
"parcelcity": "Anchorage",
"situs_zip": "99507",
"statefp": "02",
"geoid": "02020",
"longitude": -149.82953577511898,
"latitude": 61.18136645,
"usedesc": "Office Bldg - low rise 1-4 lvls",
"zoning_code": "B3",
"yearbuilt": 1981,
"taxacres": 0.64203398,
"totalvalue": 2131900,
"land_value_usd": 651400,
"improvement_value_usd": 1480500,
"market_value_usd": 2131900,
"saledate": "2021-08-23",
"updated": "2026-10-28"
}
],
"truncated": false
},
"sections": {
"utilities": {
"status": "ok",
"data": {
"water": [
{
"id": "utility:water:38542",
"feature_id": "water:38542",
"name": "MOA MUNICIPALITY OF ANCHORAGE",
"boundary_basis": "System Sourced"
}
],
"sewer": [
{
"id": "utility:sewer:3594",
"feature_id": "sewer:3594",
"name": "Point Woronzof, John Asplund WWTP",
"boundary_basis": "Modeled"
}
],
"treatment_plants": [
{
"id": "utility:treatment:2752",
"feature_id": "treatment:2752",
"name": "Point Woronzof, John Asplund WWTP",
"distance_km": 10.52886078303033
},
{
"id": "utility:treatment:2753",
"feature_id": "treatment:2753",
"name": "Eagle River WWTP",
"distance_km": 20.22932450740194
},
{
"id": "utility:treatment:15850",
"feature_id": "treatment:15850",
"name": "Goose Creek Correctional Facility WWTP",
"distance_km": 22.007686093407784
}
],
"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 02020-3313f12fb1fe809d838c, 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":"02020-3313f12fb1fe809d838c"}],"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/02020-3313f12fb1fe809d838cJavaScript
const response = await fetch(`https://api.korzy.co/v1/records/${encodeURIComponent("02020-3313f12fb1fe809d838c")}`, {
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);Anchorage Municipality data questions
- How many parcels in Anchorage Municipality include year built?
- About 87,000 of about 100,000 parcel records (87%) include year built.
- Does the Korzy API return owner names for Anchorage Municipality parcels?
- Yes. 99% of Anchorage Municipality 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 Anchorage Municipality?
- Korzy tracks 3 data-center projects in Anchorage Municipality: 3 operating. A /v1/lookup with the datacenters section lists projects within 10 km of any address or point.
- How much power generation is in Anchorage Municipality?
- 7 operable power plants in Anchorage Municipality total about 870 MW of nameplate capacity, mainly natural gas, battery and pumped storage and wind.
- Which water systems serve Anchorage Municipality?
- Service areas of about 50 community water systems cover about 13% of Anchorage Municipality, and sewer service areas cover about 6%. A /v1/lookup with the utilities section returns the water and sewer matches at an address or point.
Build on Anchorage Municipality 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.