How the data gets made

Two products, two pipelines. PermitPulse reads government short-term-rental registers on a schedule and keeps them in one file. Custom business lists are mined to the spec you set in the configurator. Below is what each one does, step by step, and what neither one does.

PermitPulse: from register to export

Read the register where the government publishes it

Each source is a list a government keeps of who may rent short-term: Florida's state licence file, city permit lists on open-data portals, county permit layers on public map services. PermitPulse reads each one through the interface its publisher offers: Florida's district files as the state's own extracts, New Orleans and Texas through Socrata open-data APIs, Portland, Denver and Traverse City through ArcGIS map services. Nothing comes from behind a sign-in. When a Florida city put its register behind a sign-in token in October 2026, pulling from it stopped.

Copy it once, then watch for what is new

The first pull of a register is a full copy. Every record that appears after that copy is tagged as new and carries the date it first reached the database, which the export calls the first-seen date. Since the first copies were taken, 12,143 new records have arrived across 35 registers. Where the register also prints a filing date, the export keeps it, so you can tell a permit filed last week from one filed in 2019 that the register only just published. The pending vs. granted guide shows how quickly each register's new filings arrive.

Clean what the registers get wrong

Registers type city names by hand, so spellings are merged before anything is counted (St. and Saint, Ft and Fort, Bch and Beach, plus a short list of known typos such as Kissimme). A record counts toward a city only when its ZIP code sits in the record's state, which drops rows filed under an owner's out-of-state mailing address. Owner and business names are grouped across distinct property addresses, so a buyer can see which names hold several rentals. Each register's own page shows what it publishes column by column, so you know before buying whether a market is a phone list or a mail list.

Leave out what is not a short-term-rental permit

Some public layers look like permit registers and are not. A city zoning map of addresses where rentals are allowed, a county parcel layer of owner names with no address, a list of residential parcels, a map of unlicensed rentals: each is named in the code and kept out of every count and export. Hotel, motel and bed-and-breakfast licence files from Florida, Wisconsin, Missouri, Denver and New Orleans are kept apart from the short-term-rental file. Idaho and Iowa are absent because their state laws stop cities from requiring the permits that would create a register (why).

Filter and export

In the account workspace you filter by state, city, permit type, filing date and contact data (phone, email, both), see the count before you spend an export, and download a CSV with every column the register published plus the first-seen date. A state plan covers one state's file; the national plan covers every state in the database. A free 25-row sample of any register comes with a free account.

Custom business lists: made to order

You set the spec

In the configurator you pick the industry, the geography and the list size, and the price updates as you go, with volume discounts applied automatically. Payment is by card through Stripe.

We mine it from public business data

The list is built from information businesses publish about themselves: name, category, address, phone, website, and email where they post it. Duplicates are removed and fields are put in one format before the file ships.

You get a CSV by email

Lists are mined after the order is placed, so delivery is not instant. The configurator states the delivery window before you pay.

What we do not do

No data from behind a login. If a publisher puts its records behind a sign-in, we stop reading it.
No consumer or credit data. No consumer leads, no credit data, no “TCPA-consented” phone lists, no UCC or court records, no skip-traced personal data.
No contact on your behalf. We do not call, text or email anyone on the lists. How you contact them is governed by the TCPA, the Do Not Call rules and CAN-SPAM, and that part is yours; the compliance guide covers the basics.
Replacement on custom lists. If a meaningful share of a custom list's records are dead or clearly wrong, flag it within 5 business days and we'll re-mine and replace them.

Start with the data.

See any register's coverage before you pay, or price a custom list in the configurator.

PermitPulse Open the configurator