PingPermit

Nightly-ingested, de-duplicated building-permit lead feed across 19 named US markets (SF, LA, Chicago, Seattle, Austin, NYC, Philadelphia, Miami-Dade, Nashville, Detroit, Las Vegas, Mesa, Marin County, Northern Kentucky, Cincinnati, New Orleans, Montgomery County MD, Louisville, Orlando), each record carrying address, neighborhood, work description, permit type, status, filed/issued dates, declared value, contractor and owner contacts where the city publishes them. Latent assets are the derived layers: a 0-100 lead score with human-readable reasons, hot/warm/cool tiering, multi-trade tagging, and per-market coverage/fill-rate measurement.

Open buyer room →

Sample

Brickroad customers

Sample this dataset before you buy it.

Your sourcing agent asks PingPermit and files the sample in your catalog — private to you.

Start 7-day trialNothing is charged until the trial ends.

Coverage

Universe, instruments and categories.

Industry: Construction & EngineeringApplication Software
Instruments: equities
Categories

Dataset card

Type: not stated
Format: Tabular - JSON REST API (bearer token) plus full-feed CSV export (/api/leads.csv); public aggregate stats and coverage endpoints unauthenticated
Volume: Rolling 45-day window, max 500 most-recent permits per API fetch, across 19 markets - so a windowed slice rather than a growing national archive. Est. low tens of thousands of permits in the live window and a few hundred thousand rows of accumulated history, well under 1GB. Live per-city counts are exposed publicly at /api/leads/coverage.
Users: N/A as a registered-user base - self-serve B2B subscription ($20/mo lead feed, $29 one-off address reports, company Data plan). No customer count published; the whole business is answered by one operator mailbox, implying a small subscriber base
History: not stated
Update frequency: not stated
Growth: Active and expanding fast from a tiny base - launched as a single-city San Francisco debris-disposal tool and grown to 19 markets with nightly refresh, a public coverage endpoint, a CSV bulk export and an API within roughly a year; still a one-operator product with no team page
Launched: 2026 (domain and first homepage snapshot detected 18 Aug 2026 as a single-city SF product; multi-market API followed within months)
Delivery: not stated
Entity mapping: not stated
Sample: not stated
Point-in-time: not stated
Licence: not stated

supplier index read from their site