Anchorage Municipality, AK parcel and infrastructure data API

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

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 Anchorage Municipality records carry an owner name.

Infrastructure in and around Anchorage Municipality

Example requests for Anchorage Municipality

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 2735 E TUDOR RD, Anchorage, AK 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=2735 E TUDOR RD, Anchorage, AK' \
  https://api.korzy.co/api/search

import os
import requests

response = requests.get(
    "https://api.korzy.co/api/search",
    params={"q": "2735 E TUDOR RD, Anchorage, AK"},
    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"])

{
  "results": [
    {
      "korzy_id": "02020-3313f12fb1fe809d838c",
      "address": "2735 E TUDOR RD",
      "city": "Anchorage",
      "postcode": "99507",
      "county": "Anchorage",
      "statefp": "02",
      "longitude": -149.82953577511898,
      "latitude": 61.18136645,
      "match_type": "exact",
      "parcelid": "00803207000",
      "parceladdr": "2735 E TUDOR RD",
      "parcelcity": "Anchorage",
      "situs_zip": "99507",
      "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",
      "geoid": "02020"
    }
  ],
  "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, 02020-3313f12fb1fe809d838c, in records. 1 credit per 10 records requested.

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

const params = new URLSearchParams({"longitude": "-149.829536", "latitude": "61.181366", "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=-149.829536' \
  --data-urlencode 'latitude=61.181366' \
  https://api.korzy.co/api/utilities/context

import os
import requests

response = requests.get(
    "https://api.korzy.co/api/utilities/context",
    params={"longitude": "-149.829536", "latitude": "61.181366"},
    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"]])

{
  "longitude": -149.829536,
  "latitude": 61.181366,
  "matches": {
    "water": [
      {
        "feature_id": "water:38542",
        "name": "MOA MUNICIPALITY OF ANCHORAGE",
        "boundary_basis": "System Sourced"
      }
    ],
    "sewer": [
      {
        "feature_id": "sewer:3594",
        "name": "Point Woronzof, John Asplund WWTP",
        "boundary_basis": "Modeled"
      }
    ]
  },
  "nearby_treatment": [
    {
      "feature_id": "treatment:2752",
      "name": "Point Woronzof, John Asplund WWTP",
      "distance_km": 10.528856903797504
    },
    {
      "feature_id": "treatment:2753",
      "name": "Eagle River WWTP",
      "distance_km": 20.22937044739646
    }
  ]
}

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. 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 Anchorage Municipality?

Korzy tracks 3 data-center projects in Anchorage Municipality: 3 operating. /api/datacenters/context lists projects within 10 km of any 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%. /api/utilities/context returns the water and sewer matches at a point.