Pulaski County, AR parcel and infrastructure data API

Korzy has about 180,000 parcel records for Pulaski County, Arkansas, with source updates through November 2026. Nearly every record carries owner names, values and land use. In and around the county the API also maps 4 data-center projects (2 operating and 1 under construction); 8 power plants with about 660 MW of capacity, led by natural gas; and about 190 miles of active rail. Look up any parcel by address or coordinates, then check water, sewer and infrastructure context at the same point.

Parcel coverage in Pulaski County

About 180,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 addressNearly all · 100%
Owner nameNearly all · 99%
Assessed or market valueNearly all · 100%
Year builtNot published
Building sizeNot published
Last saleNot published
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 Pulaski County records carry an owner name.

Infrastructure in and around Pulaski County

Power plants

8 operable plants with about 660 MW of nameplate capacity; largest by capacity: natural gas, battery and pumped storage, hydro. Proposed generators add 5 MW.

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

Substations and transmission

About 50 in-service substations, 2 rated 230 kV or higher.

About 350 miles of transmission lines: about 270 mi at 100–161 kV; about 75 mi at 500 kV.

Water and sewer service

Service areas of about 20 community water systems cover about 85% of the county.

Sewer service areas of about 15 systems cover about 29%.

At a point: /api/utilities/context

Data-center projects

4 tracked projects: 2 operating, 1 under construction, 1 proposed. Reported planned capacity: about 1,000 MW.

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

Flood zones and wetlands

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

Mapped wetlands cover about 4%.

Rail, ports and freight

  • About 190 miles of active rail, about 100 of it main line
  • About 100 miles of national freight network highway

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

Example requests for Pulaski 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 325 W CAPITOL AVE, LITTLE ROCK, AR 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=325 W CAPITOL AVE, LITTLE ROCK, AR' \
  https://api.korzy.co/api/search
Python
import os
import requests

response = requests.get(
    "https://api.korzy.co/api/search",
    params={"q": "325 W CAPITOL AVE, LITTLE ROCK, AR"},
    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": "05119-ea91be4c7bf98dbb192f",
      "address": "325 W CAPITOL AVE",
      "city": "LITTLE ROCK",
      "postcode": "72201",
      "county": "Pulaski",
      "statefp": "05",
      "longitude": -92.2744474,
      "latitude": 34.7440576,
      "match_type": "exact",
      "parcelid": "34L-020 47-000 00",
      "parceladdr": "325 W CAPITOL AVE",
      "parcelcity": "LITTLE ROCK",
      "situs_zip": "72201",
      "land_use_code": "EG",
      "taxacres": 1.61,
      "totalvalue": 338230,
      "land_value_usd": 0,
      "improvement_value_usd": 338230,
      "assessed_value_usd": 67646,
      "updated": "2026-11-03",
      "geoid": "05119"
    }
  ],
  "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, 05119-ea91be4c7bf98dbb192f, in records. 1 credit per 10 records requested.

curl --fail-with-body -sS --get \
  -H "Authorization: Bearer $KORZY_API_KEY" \
  --data-urlencode 'longitude=-92.274447' \
  --data-urlencode 'latitude=34.744058' \
  --data-urlencode 'limit=5' \
  https://api.korzy.co/api/query/point
JavaScript
const params = new URLSearchParams({"longitude": "-92.274447", "latitude": "34.744058", "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.274447' \
  --data-urlencode 'latitude=34.744058' \
  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.274447", "latitude": "34.744058"},
    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.274447,
  "latitude": 34.744058,
  "matches": {
    "water": [
      {
        "feature_id": "water:15151",
        "name": "CENTRAL ARKANSAS WATER",
        "boundary_basis": "System Sourced"
      }
    ],
    "sewer": [
      {
        "feature_id": "sewer:12",
        "name": "Little Rock - Adams Field WWTP",
        "boundary_basis": "Sourced"
      }
    ]
  },
  "nearby_treatment": [
    {
      "feature_id": "treatment:2799",
      "name": "Little Rock - Adams Field WWTP",
      "distance_km": 5.393394221720394
    },
    {
      "feature_id": "treatment:2804",
      "name": "North Little Rock - White Oak Bayou",
      "distance_km": 8.241014621698275
    }
  ]
}

Pulaski County data questions

How many parcels in Pulaski County include values?
About 180,000 of about 180,000 parcel records (100%) include values.
Does the Korzy API return owner names for Pulaski County parcels?
Yes. 99% of Pulaski 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 Pulaski County?
Korzy tracks 4 data-center projects in Pulaski County: 2 operating, 1 under construction and 1 proposed. /api/datacenters/context lists projects within 10 km of any point.
How much power generation is in Pulaski County?
8 operable power plants in Pulaski County total about 660 MW of nameplate capacity, mainly natural gas, battery and pumped storage and hydro.
Which water systems serve Pulaski County?
Service areas of about 20 community water systems cover about 85% of Pulaski County, and sewer service areas cover about 29%. /api/utilities/context returns the water and sewer matches at a point.

Build on Pulaski 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.