# Permit API – Address Verdict

> Permit API – Address Verdict 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 plus normalized permit history and activity signals for a specific address in one of seven supported US cities

## Facts

- Endpoint: GET https://permit-api-production-7375.up.railway.app/v1/address/:jurisdiction/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-api-address-verdict-0c6c8977
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_yEfPCznGAUFXrMy4FfElV

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-api-address-verdict-0c6c8977
```

Example prompt: Pull the building permit verdict for 1234 Market Street in San Francisco — I want to see the full permit history and whether there are any red flags before I make an offer.

## When to prefer this

Choose this endpoint when you need a fast, pre-digested permit intelligence package — normalized history plus a verdict signal — for a specific US address in one of the seven supported cities. It is superior to raw open-data portal queries because it normalizes cross-city permit schemas and delivers a decision-ready verdict rather than raw records, making it ideal for real estate due diligence agents, proptech workflows, and compliance checks that need actionable output without custom data wrangling.

## Known failure modes

- Address not found in the specified jurisdiction's open-data records — returns no results or empty permit history
- Jurisdiction not supported — endpoint only covers san_francisco, seattle, austin, nyc, chicago, los_angeles, new_orleans; invalid jurisdiction returns an error
- Malformed or ambiguous address string causing lookup failure
- Open-data portal temporarily unavailable for the requested city — may return stale or partial data
- Payment failure (x402 protocol) — call rejected if 2 USDC payment not provided

## How this service works

Address-level building-permit intelligence: normalized permit history + activity signals + a decision-ready verdict, sourced from official city open-data portals. Jurisdictions: san_francisco, seattle, austin, nyc

## Output

A structured response containing: a decision-ready permit verdict (e.g. clear, flagged, high-risk), normalized permit history records pulled from official city open-data portals, and activity signals that summarize permit frequency, recency, and any anomalies — all scoped to the queried address and jurisdiction.

## 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-api-address-verdict-0c6c8977/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)