Korzy API
The Korzy API gives you structured land, infrastructure, energy, environmental and logistics records for the United States as JSON over HTTPS. The same data is available to AI agents through the Korzy MCP server.
The API answers point, address and record lookups. Area and list queries are coming.
Base URL
All requests go to https://api.korzy.co. Routes live under /api. Use HTTPS only.
Quickstart
- Create an account and choose a plan.
- Create an API key on your account page. Store it as a secret, for example in the
KORZY_API_KEYenvironment variable. - Call the catalog to see what's available. Catalog requests are free.
curl --fail-with-body -sS \
-H "Authorization: Bearer $KORZY_API_KEY" \
https://api.korzy.co/api/query/catalogThen look up the parcels at a point:
curl --fail-with-body -sS --get \
-H "Authorization: Bearer $KORZY_API_KEY" \
--data-urlencode longitude=-78.6270 \
--data-urlencode latitude=35.7999 \
--data-urlencode limit=5 \
https://api.korzy.co/api/query/pointPython
import os, requests
session = requests.Session()
session.headers["Authorization"] = f"Bearer {os.environ['KORZY_API_KEY']}"
response = session.get(
"https://api.korzy.co/api/search",
params={"q": "714 Mordecai Towne Pl, Raleigh, NC"},
timeout=30,
)
response.raise_for_status()
for result in response.json()["results"]:
print(result["match_type"], result["address"], result.get("korzy_id"))JavaScript
const response = await fetch(
"https://api.korzy.co/api/parcel-record?" + new URLSearchParams({ korzy_id: "37183-676db8ae68362b7a3685" }),
{ headers: { Authorization: `Bearer ${process.env.KORZY_API_KEY}` } },
);
if (!response.ok) throw new Error(`${response.status}: ${await response.text()}`);
const parcel = await response.json();
console.log(parcel.parceladdr, parcel.usedesc, parcel.totalvalue);Conventions
- Coordinates are WGS 84 longitude and latitude in decimal degrees. Bounding boxes are
west,south,east,north. - Responses are JSON. Missing values are
null; a null value means the source didn't publish it, not that it's zero. - Values keep the units and dates their sources publish. Read the unit and date fields alongside each value.
- IDs are opaque strings. URL-encode them in paths and query strings.
- New fields can be added to responses at any time. Ignore fields you don't recognize.
Next
- Authentication: keys, scopes and sign-in for agents.
- Credits, limits and errors: what requests cost, rate limits, pagination and status codes.
- API reference: every route and its parameters.
- MCP server: connect Claude, ChatGPT, Codex and other agents.