Zoning Lookup: What Can Be Built Here

A zoning lookup API by address: feed it a US address (or lat/lng), get back the parcel's zoning as structured data instead of an undecipherable code string — the raw district code, a normalized land-use category, allowed uses, nuisance level, overlays, a rezoning flag, a confidence level, and a short plain-English narrative. Built for site due diligence, land acquisition screening, permit research, and "what can be built at this address?" questions — one address or a scripted pipeline of thousands.

• Input: { "address": "600 Congress Ave, Austin, TX" } or { "lat": 30.27, "lng": -97.74 }
• Returns: the shared Plat envelope: schema_version, address, coverage, zoning, meta.

Common uses: zoning verification for real-estate listings, checking allowed uses before an offer, flagging rezoning candidates across a portfolio, feeding a GIS or underwriting pipeline with normalized zoning categories.

Coverage

• Full interpretation (28+ authored markets): Austin, Dallas, Fort Worth (conventional districts only — its form-based districts return cited zone codes), Chicago, Phoenix, Denver, Seattle, Atlanta, Miami, Nashville, Albuquerque, Santa Fe, Las Cruces, Houston (where "unzoned" is the honest, first-class answer — the city has no zoning ordinance), and the authored Texas metro suburbs incl. Rockwall and Forney. Raw code resolved to allowed uses, overlays, confidence, and a plain-English narrative. Each named city is verified with live production lookups.
• Cited district codes: Los Angeles, San Diego, Long Beach, Detroit, Cleveland, and — first international coverage — Vancouver, BC and Toronto, ON (coordinates or full addresses; Toronto answers carry an explicit appeal-status field so a district under appeal is never presented as operative law), plus additional DFW-area cities. All live-verified against each city's own GIS. The real district code is returned; the full allowed-use interpretation is not yet authored for those cities — the response says so honestly instead of guessing. These answers are real coverage: coverage.sections_available lists zoning and coverage.tier reads "cited", so a caller reading the coverage block first never skips a section that did answer. The tier is per ANSWER, not per city: an authored city reads "interpreted" for a code its table carries and "cited" for one it does not — so budget against the answer you get, not the city you asked about.
• Everywhere else: the zoning section is null by coverage and the envelope explains why. It does not invent a code for a place we haven't authored.

Telemetry

This Actor sends an anonymous coverage signal (county-level only, never the address, the report, or your identity) so we can see where to add coverage next.

Want your market covered?

Full interpretation is authored city by city, demand-first. If you need allowed uses and rezoning flags in your market (Chicago, Detroit, LA, anywhere), email support@platreport.com (or reach Will directly: will@platreport.com) with the counties you care about — the most-requested jurisdictions get authored next.

Plat links — by need

• Want the full visual report instead of JSON? platreport.com — same data spine, human-readable, free sample.
• Support, data problems, or "cover my market next": platreport.com/contact or support@platreport.com.
• Composing several Plat tools from an agent? platreport.com/AGENTS.md — the whole suite, input shapes, and schema notes in one machine-readable page.

---

Built by Plat. Try the full report free at platreport.com