What is this parcel, who holds authority over it, what will the code demand, and what has already been built here. PropDocket answers all four from one address.
Pick a property and watch the report assemble. That trace is the same sequence of calls an agent makes — no scraping, no screenshots, no waiting on a county portal to wake up.
Sample data for illustration. Live reports run against Florida DOR parcel records, FEMA, ASCE, USGS, and jurisdiction permit portals.
What it does
Parcel search
Look up any Florida parcel by address, parcel ID, owner name, or coordinates. Backed by a cached statewide Department of Revenue parcel set, with a live ArcGIS fallback when the cache misses.
Returns owner, square footage, year built, just / assessed / land value, sale history, legal description, and township-range-section.
Jurisdiction context
The county and building department that actually hold authority over an address — plus that jurisdiction's permit portal, property appraiser, GIS, and flood map.
The part that usually costs twenty minutes and three browser tabs.
Hazard data
FEMA flood zone, base flood elevation, and special flood hazard area. ASCE wind speeds by risk category and seismic parameters by site class. Estimated ground elevation.
Numbers an engineer can put on a drawing, not a summary of numbers.
Permit history
Status, inspections, documents, and workflow for a permit — plus every permit recorded at a property, and every permit filed under a contractor license.
Due diligence, closeout research, and finding out who has actually touched a building.
Access
Built for people and agents equally
PropDocket is a REST API and an MCP server. A person queries it through an interface; an agent queries the same data through the same contract — no scraper, no screenshot, no one-off integration standing in between.
Interfaces
REST · MCP
Coverage
Florida
Parcel source
Florida Department of Revenue, cached, with live ArcGIS fallback
Hazard sources
FEMA flood · ASCE wind and seismic · USGS elevation