Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.permitcore.io/llms.txt

Use this file to discover all available pages before exploring further.

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
MAPPED18 metrosFull ingest active. Daily refresh. Cohort classification + DQ flags inline. Parcel-joined geometry where the metro publishes it.
SOURCE5 metrosBronze ingest active. Sample-tier rows visible. MAPPED promotion in production-ingest queue (Q3 2026).
DEPLOY-PENDING3 metrosCode merged; production-ingest queue rollout Q3 2026. No live data yet.
The 26 metros today cover the top US metros by permit volume; expansion follows a defined cohort coverage roadmap.
  • MAPPED (18): NYC, LA, Chicago, Houston, SF, Seattle, Boston, Atlanta, DC, Dallas, Philadelphia, San Diego, Charlotte, Nashville, Columbus, Indianapolis, Fort Worth, San Antonio.
  • SOURCE (5): Phoenix, Austin, Miami, Portland, Las Vegas.
  • DEPLOY-PENDING (3): Denver, Oklahoma City, Jacksonville.

​
Status meanings

​
MAPPED

The metro’s full permit feed is ingested daily, 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. Promotion ETA: Q3 2026 per current roadmap.

​
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: Q3 2026.

​
Slug list

Browse all 26 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 — daily refresh cadence + as_of_utc interpretation
  • Data licensing — commercial-use terms + attribution