PermitReporterKnow what’s breaking ground.
Get Lead Alerts
Get Lead Alerts

Permit intelligence for people and agents

Search Georgia permits
from the conversation.

PermitReporter gives compatible AI assistants direct access to source-linked building-permit records, exact county coverage boundaries, contractor opportunity signals, and—only when you authorize it—a real double-opt-in email watch.

11,830
permit records collected
25
counties represented by permit records
159
Georgia county pages
2026-08-11
latest represented permit date

A public interface with receipts

Find the record.
Keep its source attached.

Public reads stay privacy-minimized. Every permit result preserves the date, source, collection timestamp, canonical citation, and the limits of the route that produced it.

01

Search permits

Look up collected building permits by public text, county, city, address, trade classification, or date range.

02

Check coverage

Distinguish live and lagged record routes from counties where the page carries only a statistical floor.

03

Find contractor signals

Explore source-linked trade and project-scope classifications without treating an editorial signal as guaranteed work.

04

Create a watch

With your explicit permission, an agent can create a pending email watch. Alerts stay off until you confirm the address.

Double-opt-in alerts

Let PermitReporter keep watch.

Create the same pending watch a compatible agent can create. We store the email, query, optional county, confirmation state, and a private unsubscribe token. No alerts begin until the address is confirmed.

A watch is not a completeness guarantee. It matches records that enter PermitReporter's collected layer; it does not monitor every government system or file a permit.

By filing this watch, you ask PermitReporter to send a confirmation email and accept the Terms and Privacy Policy.

Open agent access

MCP for the conversation.
OpenAPI for everything else.

Read tools are public. The only write is an additive, idempotent pending watch with explicit consent fields and required email confirmation.

Remote MCP serverhttps://permitreporter.com/mcp
Official MCP Registry namecom.permitreporter/georgia-permits
OpenAPI 3.1 contracthttps://permitreporter.com/openapi.json
Public read APIhttps://permitreporter.com/api/agent
Authorized watch actionPOST https://permitreporter.com/api/agent/watches
AI citation maphttps://permitreporter.com/ai-citation-map.json

The agent contract

  • Call the county-coverage tool before interpreting a missing result.
  • Preserve the canonical record, official source, record date, collection timestamp, and stated limit.
  • Never expose or infer raw payloads, owner or applicant party arrays, emails, confirmation tokens, or internal enrichment state.
  • Create a watch only after the user reviews the exact details and explicitly authorizes the action and confirmation email.
No matching record collected is not the same as no permit exists.

Government systems differ by issuer, access method, cadence, history, and reliability. PermitReporter reports the collected layer and makes the boundary visible.

Inspect county coverage