# Permit Verdicts API

> Permit Verdicts API is a paid API for AI agents from permit-api-production-7375.up.railway.app, paid per call via x402, $2/call, status unknown (last checked 2026-09-14).

Returns a decision-ready building permit verdict with normalized permit history, activity signals, and cited public records for a given address and jurisdiction.

## Facts

- Endpoint: GET https://permit-api-production-7375.up.railway.app/v1/address/%7Bjurisdiction%7D/verdict
- Price: $2/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/permit-verdicts-api-7131efda
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_C9pifr8dF0X_MDONs3pqY

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability permit-verdicts-api-7131efda
```

Example prompt: Can you pull the permit verdict for 742 Evergreen Terrace in Springfield, IL — I want to know the full permit history, any recent activity signals, and whether there are any red flags before I make an offer?

## When to prefer this

Choose this endpoint when you need a structured, decision-ready verdict on a property's permit history rather than raw municipal data. It is ideal for real estate due diligence, pre-purchase inspection workflows, lender underwriting, or contractor compliance checks where a normalized, cited output is needed immediately without manually querying multiple jurisdictions.

## Known failure modes

- Jurisdiction not supported — permit data not available for the requested jurisdiction
- Address not found — the address cannot be matched to public permit records
- Payment failure — x402 payment of $2 USDC not processed or insufficient balance
- Rate limiting — too many requests in a short period
- Stale data — permit records may lag behind real-time municipal updates
- Ambiguous address — multiple matches found requiring disambiguation

## How this service works

Address-level building-permit intelligence: normalized permit history, activity signals, and a decision-ready verdict with cited public records. Paid per call via x402.

## Output

A structured response containing a decision-ready permit verdict (e.g. clear, flagged, or review needed), a normalized history of building permits associated with the address, activity signals indicating recent or unusual permit activity, and citations to the underlying public records used to generate the verdict.

## Request schema (JSON Schema)

```json
{
 "properties": {
  "input": {
   "type": "object",
   "required": [
    "type",
    "method"
   ],
   "properties": {
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "GET"
     ],
     "type": "string"
    },
    "pathParams": {
     "type": "object"
    }
   },
   "additionalProperties": false
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/permit-verdicts-api-7131efda/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from permit-api-production-7375.up.railway.app](https://www.zero.xyz/host/permit-api-production-7375.up.railway.app/llms.txt)