For Developers

Florida property data with a contract you can rely on

A standards-compliant MCP server and a plain REST API over Florida parcels, jurisdictions, hazards, permits and zoning. Scoped keys, honest provenance, no sales call.

You have integrated a property API before. You know how it goes.

The failure modes are always the same, and they are always discovered in production.

A response returns a value with no indication of whether it is authoritative, stale, or a guess

Every value carries its source and date, and says whether it was verified against the record or compiled from the ordinance

A fuzzy address match silently resolves to the wrong parcel and nothing in the payload says so

`match_method` on every property response. An exact match says exact; anything else says what it actually did

An upstream source is down, the API returns 200, and a field is quietly absent

`missing_sources` lists what could not be reached, so a gap is a value in the payload rather than an inference you have to make

Pricing is behind a form and the rate limits are discovered by hitting them

PropDocket is free during the beta. No card required. We'll email you before billing starts. Published limits remain in the contract.

The surface

Two transports over the same contract. Use whichever fits — an agent and a cron job get the same guarantees.

Sample Report Data

MCP

Streamable HTTP

Protocol

2026-07-28

REST

JSON over HTTPS

Auth

OAuth 2.1 / bearer

Scopes

property · permit · zoning

Key rotation

Self-serve

Coverage

Florida

Every response

request_id

Bring your own AI agent

Narrow tools, so agents do not burn context

A property report is a large object. Handing an agent the whole thing on every call is how you exhaust a context window and a budget at the same time.

Ask for exactly one thing

Narrow tools are the documented default — flood, wind, seismic, permit status, each on its own. Fetch the full report only when you actually need it.

Field projection

Ask for the fields you want and get those. The default payload is deliberately small; breadth is opt-in rather than the price of admission.

It files its own bug reports

A `submit_feedback` tool lets an agent report a failed lookup or a data mismatch with the request_id and provenance snapshot attached, without a human writing a ticket.

Ask your agentexample

Add PropDocket over MCP, then: "What is the flood zone and design wind speed at 1200 Brickell Ave, and what sources did that come from?"

How it works for you

1

Enrich an existing product

Add jurisdiction, hazard and permit context to a CRM, a quoting tool, or an underwriting workflow without building 30 portal scrapers and maintaining them forever.

2

Give your agent a tool

If you are already shipping an assistant, this is one MCP connection away from answering Florida property questions with cited data instead of recalled approximations.

3

Batch and backfill

Run a portfolio through the REST API to populate hazard fields you never had. Rate limits are published so you can plan the run rather than discover the ceiling.

Questions we actually get

Is there an MCP server?

Yes. Connect any MCP client to https://mcp.propdocket.com/mcp, sign in with your PropDocket account, and your agent has every tool. Setup steps for each client are on the MCP page.

How do I know whether a value is trustworthy?

Every value carries its source and date, and says whether it was verified against the record or compiled from the ordinance. Responses also say how the address matched and name any source that could not be reached, so a gap is a value you can read rather than a field you have to notice is missing.

Do I have to fetch the whole property report every time?

No. Narrow tools are the documented default — flood, wind, seismic, permit status each on their own — and field projection is supported. Breadth is opt-in rather than the price of a single lookup.

Do I need to talk to sales to get a key?

No. PropDocket is free during the beta. No card required. We'll email you before billing starts.

What happens when an upstream source is down?

The response still returns, and missing_sources names what could not be reached. We do not return a 200 with a silently absent field.

PUBLIC BETA

PropDocket is free during the beta. No card required. We'll email you before billing starts.

Usage-based, one balance per organization, no seats, nothing expires. See pricing →

Stop toggling between tabs.
Start making decisions.

Get instant property intelligence for any Florida address. Free during launch — no credit card required.

Create a free account