Skip to main content
A jurisdiction is a single city or metro area that PermitCore ingests permits from. Identified by a lowercase URL-safe slug (nyc, la, houston).

​
Coverage today

StatusCountWhat this means
MAPPED21 metrosFull ingest active. Refreshed nightly. Cohort classification + DQ flags inline. Parcel-joined geometry where the metro publishes it.
DEPLOY-PENDING4 metrosCode merged; production-ingest queue rollout coming soon. No live data yet.
The 25 metros today cover the top US metros by permit volume; expansion follows a defined cohort coverage roadmap.
  • MAPPED (21): NYC, LA, Chicago, Houston, Phoenix, SF, Austin, Seattle, Boston, Atlanta, Miami, Denver, DC, Philadelphia, Charlotte, Portland, Nashville, Las Vegas, Columbus, Fort Worth, San Antonio.
  • DEPLOY-PENDING (4): Dallas, Indianapolis, Jacksonville, Oklahoma City.

​
Status meanings

​
MAPPED

The metro’s full permit feed is ingested nightly, classified to the canonical 18 cohorts, DQ-flagged at the field level, and parcel-joined to PLUTO or the local equivalent where available. API requests against a MAPPED metro return real production data.

​
SOURCE

Bronze ingest is active — raw permits are flowing into PermitCore — but cohort classification, DQ flagging, and parcel join are queued for production promotion. API requests against a SOURCE metro return sample rows, NOT the full feed. No metros are in this state today; the bucket is preserved for future bronze-ingest metros on their way to MAPPED.

​
DEPLOY-PENDING

The ingest pipeline code is merged but not yet running in production for this metro. API requests return no data; the cohort distribution endpoint returns 404 for these slugs. ETA: coming soon — pipeline pings per-metro on ship.

​
Slug list

Browse all 25 metro pages: permitcore.io (metro tiles on the homepage). A complete machine-readable list is available in the cohort-distribution endpoint’s behavior: any slug that returns 200 (vs 404) is a metro PermitCore has any data for.
  • Cohorts — the 18-cohort taxonomy that classifies every permit
  • Data freshness — nightly refresh cadence + as_of_utc interpretation
  • Data licensing — commercial-use terms + attribution