Permiva compiles public building-permit records from the jurisdictions that issue them. This page explains how to read an answer correctly, what the data cannot tell you, and what we do with what you send us.
Permiva is operated by Two Leos Inc., a Florida corporation, of 1500 Presidential Way, Suite 503, West Palm Beach, FL 33401. In these terms, "Permiva", "we" and "us" mean Two Leos Inc.
Permiva is an informational data service. We gather building-permit records from Florida jurisdictions, normalise them into one form, and let you look up what those records say about an address — through this site or the API.
We are not a consumer reporting agency, an inspection service, an insurer, a surveyor, or a provider of professional advice. Nothing here is a valuation, an underwriting decision, a coverage determination, a title opinion or a property condition report. Using the service does not create a professional relationship of any kind.
By using the site or the API you accept these terms. If you are accepting on behalf of an organisation, you confirm you may bind it.
Every record originates with the authority that issued the permit — a city or county building department. We collect it from their public portals, published open-data feeds and, where a portal does not reach far enough back, from public-records requests to the jurisdiction itself.
Those sources do not resemble one another. Florida jurisdictions run at least eight different permitting platforms between them, and a single jurisdiction often has two eras — a legacy system holding the history and a newer one holding everything since it was replaced. We normalise addresses, dates, statuses and permit descriptions so all of it can be read the same way, and we join the eras at the seam.
That normalisation is our work, and it is where our errors live. The underlying records belong to the issuing jurisdictions and remain public. Anything we report can be checked against the source, and we would rather you checked it.
When a lookup returns COVERED_NO_PERMIT, it means no roofing
permit for that address appears in our records for that jurisdiction,
within the historical depth we hold for it. It does not mean the roof was
never replaced. Work may predate our earliest record, may have been done
without a permit, may sit under an address that did not match, or may not
have reached the jurisdiction's public portal yet.
NOT_COVERED is a different answer again: it says we do not
hold that jurisdiction at all. Collapsing the two is the most common way to
misread this data, which is why the API keeps them apart, and why a failed
lookup is its own state rather than an empty result.
Some jurisdictions we hold from the late 1980s. Others begin in the 2010s or later, because that is when the jurisdiction's own system begins. A "no permit" answer means very different things in those two places, and the difference is not a footnote — it is the whole interpretation.
Every answer carries records_from for exactly this reason, and
the coverage page publishes the
floor year, permit count, newest permit and date precision for every
jurisdiction we hold. Read an answer against that, never on its own.
We report the date the jurisdiction records against the permit, and what that date represents is not uniform. Most record the date a permit was issued. Some record the application date. A few record the date the permit's status last changed, so a permit issued in one year and finalled in the next carries the later date.
For roof age this rarely matters by more than a few months. For anything turning on a precise date, verify with the issuing jurisdiction.
Most jurisdictions record the day. Some publish only the month, and at
least one records only the year; for those the date is placed mid-period
and the precision field says so. That is accurate enough for
roof age and not for anything finer. Precision is never quietly inferred.
We would rather state these plainly than have you find them:
Jurisdictions are added as we build them, and a jurisdiction's depth can improve — a records request or a newly found legacy archive can move a floor year back by decades. Depth can also move the other way if a source is withdrawn or found unreliable, and if that happens we would rather hold less data than data we cannot stand behind.
The coverage page and the coverage endpoint are the current statement of what we hold. Neither this page nor any conversation supersedes them.
Permiva does not warrant that a search represents the complete permit history of a property. Results should not be relied upon as the sole basis for underwriting, rating, eligibility, non-renewal, cancellation, claims, valuation, lending or purchase decisions.
The service and the data are provided as is and as available, without warranty of any kind, express or implied, including any implied warranty of merchantability, fitness for a particular purpose, accuracy, or non-infringement. We do not warrant that the service will be uninterrupted or error-free.
To the fullest extent permitted by law, Permiva is not liable for any indirect, incidental, special, consequential or punitive loss, nor for lost profits, lost business or lost data, arising from use of or reliance on the service. Our total aggregate liability for any claim is limited to the amount paid for the service in the twelve months before the claim arose.
Where a decision affects someone's cover, premium or claim, verify the record with the issuing jurisdiction. Every answer names the jurisdiction, and carries the permit number where the source provides one, so that you can.
An API key is issued to one organisation for that organisation's own use, and is confidential. You are responsible for what happens under your key; tell us promptly if you think it has been exposed and we will reissue it.
In using the service you agree not to:
Using results inside your own systems, reports, models and decisions is exactly what a key is for, and so is showing an answer to the customer it concerns. The line is redistribution of the data itself.
We may suspend or withdraw a key used in breach of this, and we will say why. You may stop using the service at any time.
This is a working service, not a frozen one. Endpoints may gain fields; existing fields will not change meaning without notice to key holders. Refreshes run continuously, and the newest-permit date shown against each jurisdiction tells you how current that one is. Limits are stated in the API documentation and agreed when a key is issued.
We may change these terms as the service changes, and the date at the top says when they last moved. Material changes to acceptable use or to liability are emailed to key holders rather than only posted here.
Two Leos Inc. is responsible for the information described here. We collect very little, because the service does not need much.
We do not sell personal information. We do not run advertising or behavioural trackers on this site. We use a small number of service providers to host the site and send email; they handle data only on our instructions.
Owner names appearing in permit records are public information published by the issuing jurisdiction. We do not enrich them and we do not combine them with data from other sources.
Permiva and Lead-Spy read the same permit records. They do not share customer data in either direction. An address a carrier looks up here does not become a roofing lead there.
To ask what we hold about you, to correct it, or to have it deleted, email gabor@permiva.ai. If a permit record itself is wrong, the issuing jurisdiction holds the original and is the only party that can amend it — tell us as well and we will reflect the correction once they make it.
These terms are governed by the laws of the State of Florida, where Two Leos Inc. is incorporated, without regard to its conflict-of-laws rules. The state and federal courts serving Palm Beach County, Florida have exclusive jurisdiction over any dispute arising from them.
If any part of these terms is unenforceable, the rest continues to apply. Not enforcing a term on one occasion is not a waiver of it.
Questions about any of this, including anything this page should have answered and did not — gabor@permiva.ai.
Two Leos Inc.
1500 Presidential Way, Suite 503
West Palm Beach, FL 33401