For proptech & investors

Permit history your model can defend

Feed your models clean North Carolina permit history instead of scraped county HTML, so every feature traces back to a filing you can point at.

Built for

Data and product teams

One North Carolina address format, one filing schema, and a stable history you can rebuild features from months later.

Under the hoodComing soon

The data API isn't available yet. These examples show what it will look like when it launches.

Match an address to a stable North Carolina record

GET /nc/v1/match?address=1420 Oberlin Rd&city=Raleigh&zip=27605

Returns the matched parcel reference and a match score, so bad joins fail loudly instead of silently.

Pull the full filing history

GET /nc/v1/permits?parcel=nc-wake-0794123456&include=milestones

Every filing we hold for that property: type, scope, stated value, contractor and inspection dates.

Roll it up for market features

GET /nc/v1/trends?scope=zip&zip=27605&window=12m&group_by=trade

Monthly counts and values by trade, ready to drop into a feature table.

What changes

Features you can explain in a diligence call, because each one links back to a municipal filing.

One consistent shape across every North Carolina county, so you stop writing per-jurisdiction parsers.

Renovation and improvement history you can use to separate touched stock from untouched.

Where to begin

Pick one or two to start. Once you can see which ones turn into work for you, widen the net.

nc.property.improvements

Permits filed against a property over time, with stated scope and declared value.

Good for: Condition adjustments, rehab detection and comp screening.

nc.market.activity

Monthly filing counts and declared values by ZIP, city or county.

Good for: Supply-side features and market-level demand indicators.

Keep reading

No card, no contract. Tell us your ZIP and the first list lands in your inbox right away, then every Monday morning.