Data licensing
Structured, source-cited building-permit data — fees, timelines, documents, codes, and per-record verification dates — licensed for commercial use, with bulk delivery, a change-feed, and an SLA.
- States
- 8
- Jurisdictions
- 552
- Permit types
- 5727
Who licenses this
Proptech & construction software
Show real permit requirements, fees, and timelines inside your product instead of sending users to a dozen municipal PDFs.
Lenders & construction finance
Underwrite draw schedules and project timelines against verified review-time and fee data, not estimates.
Insurers & risk
Ground inspection and code-adoption assumptions in each jurisdiction's actual adopted codes and amendments.
Permit expediters & consultants
Run intake and quoting from one normalized dataset across every market you serve.
The data is free. The license buys everything around it.
Every fact PermitBase publishes is free forever — on the site, as keyless static JSON, and through our free JSON API & MCP server. No fact ever moves behind a paywall. A commercial license adds what teams actually need in production: bulk delivery (one versioned archive and flat CSV/NDJSON exports instead of hundreds of per-jurisdiction files), a structured change-feed (per-release diffs by webhook, instead of re-crawling), an SLA (delivery guarantees, verification cadence, priority re-verification), and written commercial rights to embed and redistribute the data inside your product.
Licensing tiers
Internal
From $299/mo
Invoiced annually
Teams using the data inside their own workflows — permit expediters, lender ops, underwriting research.
- Quarterly bulk archive of the full dataset (every jurisdiction file + coverage, one download)
- Flat CSV/NDJSON exports normalized for your pipeline
- Dataset-wide change digest by email at every data release
- Internal-use license (written grant)
- Standard email support
Most common
Product
From $999/mo
Invoiced annually
Companies embedding permit data in a customer-facing product — proptech, insurtech, construction fintech.
- Everything in Internal
- Redistribution & derivative-use rights inside your product (written grant)
- Structured change-feed per data release — what changed, where, old → new — by webhook or feed file
- Delivery SLA and guaranteed response times, set in the agreement
- Priority re-verification requests for jurisdictions you depend on
- Named contact
Enterprise / Partner
Custom
Annual agreement (MSA)
Custom coverage, custom schema, or contractual terms your legal team needs.
- Everything in Product
- Sponsored coverage expansion — the jurisdictions or states you need move to the front of the verification queue
- Custom delivery format and cadence
- Custom SLA and MSA terms
Prices are indicative. Licensing isn’t open yet — leave your email below and we’ll reach out the moment it is.
Why this dataset is different
Every record is chased to a governing published source — ordinance, adopted fee schedule, or statute — and carries its own citation and lastVerified date. Requirements freshness and Census building-activity vintage are tracked separately and never conflated. Each data release is identified by a content hash of the source files, so a change in the dataset version means the data itself changed — the anchor the change-feed diffs against. Nothing is averaged, extrapolated, or inferred: a field we couldn't verify is absent, not guessed.
Frequently asked questions
- Isn't all of this data already free?
- Yes — every fact is free and stays free, on the site, as static JSON at /data/v1/, and through our MCP server. A license doesn't buy the facts. It buys delivery (one bulk archive and flat exports instead of 334 individual files), a machine-readable change-feed, contractual SLA and verification guarantees, and written rights to redistribute the data inside your product.
- Why is there no checkout?
- Data licensing starts with a short call so we can scope delivery format, change-feed mechanics, and license terms to your use — then we bill by invoice. There is deliberately no self-serve charge.
- What does the change-feed contain?
- Every data release carries a content-hashed dataset version. Licensed customers get a structured diff per release — which jurisdiction, which permit type, which field, old and new value — instead of re-crawling the dataset to find changes.
- Can you cover a jurisdiction we need that isn't listed?
- Enterprise / Partner agreements can sponsor coverage expansion: the jurisdictions or states you depend on move to the front of our verification queue, researched to the same source-cited bar as everything else.
- Is this legal advice?
- No. Licensed data carries the same disclaimer as the site: it is a source-cited reference, verified against official sources and dated per record, but requirements change and the issuing jurisdiction always has the final word.