Municipal and agency records
Permits, inspections, code activity, certificates, planning records, licensing, registrations, and posted notices.
Custom Data Feeds
Need a public source pulled every week? Ask PermitPub to build the feed.
PermitPub is built to find useful signals in public data. If we are not already pulling the source you want, and the data is publicly available and crawlable, we can evaluate it, scope it, and quote a custom feed.
It does not have to be strictly building permits. If the source creates sales intelligence, market intelligence, compliance intelligence, or operational data your team can act on, bring it to us.
What can become a feed?
Public records, open data, portals, dashboards, PDFs, and other crawlable sources.
Open-data portals
City, county, state, or federal datasets published through open-data platforms, downloads, APIs, CSVs, or maps.
Sales trigger sources
New business activity, bid postings, occupancy signals, contractor opportunities, property events, or other buying signals.
Market watchlists
Sources your team checks manually today that should be monitored, cleaned, filtered, and turned into a usable feed.
How it works
We scope the source before quoting the feed.
- You send us the source, market, and what records matter.
- We check whether the data is public, crawlable, and stable enough.
- We test a small sample and define the fields, filters, and refresh schedule.
- We quote the setup, monthly maintenance, and delivery format.
What you get
Clean data your team can use.
- Filtered records instead of raw noise
- Useful fields normalized where possible
- Refresh cadence matched to the source
- CSV, dashboard, or private delivery options
- Monitoring for failed or stale sources
Important limits
Custom feeds are for publicly available sources, not private databases.
We will not bypass logins, scrape private accounts, break paywalls, or pull sources that prohibit access. A custom feed has to be based on public information or a source you have the right to provide.
Some public sites are still poor candidates because they are unstable, incomplete, blocked, or too expensive to monitor. If that happens, we will tell you directly instead of selling a bad feed.
We also reserve the right to decline custom feed requests that create privacy, safety, harassment, doxxing, surveillance, or compliance concerns, even if some underlying information is public.
Custom quote factors
Pricing depends on the source, volume, cleanup, and delivery.
Source complexity
A simple CSV or open-data API is different from a city portal, map layer, PDF archive, or source that changes often.
Refresh cadence
Daily, weekly, monthly, or event-based updates change the monitoring and compute needed to keep the feed useful.
Data cleanup
Deduping, category rules, value parsing, address normalization, and enrichment add value but also affect scope.
Delivery
Private CSV delivery, dashboard access, custom exports, alerts, or API-style handoff can be quoted separately.
Good custom feed requests sound like this:
- "Pull new restaurant inspections in these counties every week."
- "Watch this city portal for new certificate of occupancy records."
- "Track contractor licensing changes in these states."
- "Turn this public bid board into a filtered sales feed."
Weak requests sound like this:
- "Find anything that might be useful."
- "Scrape a private site I log into."
- "Pull data from a source that blocks or forbids crawling."
- "Guarantee every record is complete when the public source is incomplete."
Bring us the source
If your reps need a public signal, we can evaluate the feed.
Send the source, the market, the fields you care about, and how often you want it refreshed. PermitPub will tell you whether it is realistic and what it would cost.