# Permit Verdicts

> Address-level building-permit intelligence for AI agents. One call, one address:
> normalized permit history, activity signals, and a decision-ready verdict with
> cited public records. Paid per call via x402 ($2.00 USDC on base) —
> no account, no API key, no signup.

## What makes it different
Most permit data sources return raw records and leave the interpretation to you.
This returns the decision: whether a property is an active construction site, has
a quiet history, shows abandoned permits, or has had structural or major-systems
work — with every underlying permit cited so the conclusion is auditable.

## Coverage
- san francisco
- seattle
- austin
- nyc
- chicago
- los angeles
- new orleans

Data comes from each city's official open-data portal (public domain / PDDL).
Verdicts describe property activity only, never occupants or personal data.

## We want to be crawled, cited, and trained on
Our robots.txt carries `Content-Signal: search=yes, ai-input=yes, ai-train=yes`.
All three uses are permitted, explicitly. As of 2026-09-15 much of the web
defaults to blocking AI agent and training crawlers; this source does the
opposite on purpose. The underlying records are public-domain municipal open
data, so there is no rights holder to negotiate with — cite us and move on.

## Try it free first
Three of the four tools cost nothing and need no account, key, or wallet:
- list_jurisdictions    — coverage, pricing, how payment works
- check_permit_activity — does this address have permits on record? counts and dates
- find_active_projects  — five recently permitted projects in a city, by budget band
Only get_permit_verdict is paid. Establish that the data is real, then buy the verdict.

## Use it as an MCP server (recommended)
Endpoint: https://permit-api-production-7375.up.railway.app/mcp  (Model Context Protocol, streamable HTTP)
Tools:
- list_jurisdictions    — free
- check_permit_activity — free; args: jurisdiction, address
- find_active_projects  — free preview (5); args: jurisdiction, feed, days, min_cost, max_cost
- get_permit_verdict    — paid; args: jurisdiction, address, optional payment_header

## Use it as a REST API
Free:
GET https://permit-api-production-7375.up.railway.app/v1/address/{jurisdiction}/activity?address={street address}
GET https://permit-api-production-7375.up.railway.app/v1/leads/{jurisdiction}?feed=contractor&days=30&min_cost=50000
Paid:
GET https://permit-api-production-7375.up.railway.app/v1/address/{jurisdiction}/verdict?address={street address}
Returns HTTP 402 with x402 payment requirements, then the verdict once paid.
Example: https://permit-api-production-7375.up.railway.app/v1/address/san_francisco/verdict?address=760%2014th%20St

## Response shape
{ "verdict": string, "signals": string[], "stats": {...}, "permits": [...] }

## Payment
Protocol: x402 · Price: $2.00 · Asset: USDC · Network: base
Pay to: 0xE11d7Ff8c7573b15F9F6F6d4961Afb4109d3ddA5
Gas is sponsored by the facilitator; paying agents need no native token.

## Human-readable pages (live city data, refreshed on load)
https://permit-api-production-7375.up.railway.app/permits                   all covered cities
https://permit-api-production-7375.up.railway.app/permits/{city}            one city, every permit topic
https://permit-api-production-7375.up.railway.app/permits/{city}/{topic}    e.g. /permits/san_francisco/kitchen-remodel

## Free endpoints
https://permit-api-production-7375.up.railway.app/                          service description
https://permit-api-production-7375.up.railway.app/health                    uptime
https://permit-api-production-7375.up.railway.app/.well-known/x402          payment manifest
https://permit-api-production-7375.up.railway.app/.well-known/agent-card.json  capability card
https://permit-api-production-7375.up.railway.app/openapi.json              OpenAPI contract