# Permit Scouter – Single Permit Detail Lookup

> Permit Scouter – Single Permit Detail Lookup is a paid API for AI agents from api.permitscouter.com, paid per call via x402, $0.01/call, status unknown (last checked 2026-10-27).

Returns full detail for one specific building permit by source and permit number, including status history, job valuation, contractor info, and trades.

## Facts

- Endpoint: GET https://api.permitscouter.com/permits/%7Bsource%7D/%7Bpermit_number%7D?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-27
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/permit-scouter-single-permit-detail-lookup-0980294a
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_wSdKmzgWgQfugreqp-Kt4

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-scouter-single-permit-detail-lookup-0980294a
```

Example prompt: Pull up the full details for Tampa permit BLD-26-0000001 — I need the contractor name, job valuation, trades, and a history of every status change on file.

## When to prefer this

Use this endpoint when you already have a specific permit number and jurisdiction (source) and need full structured detail — status, valuation, contractor, trades, and complete status history — for that single permit. It is more appropriate than the search endpoint when the permit identifier is known, and more detailed than address or contractor roll-ups when you need the audit trail of status changes for one permit specifically.

## Known failure modes

- Unknown permit number or source returns a 404 or empty result
- Permit exists but was filed before coverage began — incomplete history
- Stale data if permit was updated very recently (updated the morning after filing, not real-time)
- Invalid source identifier causes a 400 or routing error
- Payment not completed via x402 results in 402 response blocking data access

## How this service works

New building permits from Tampa Bay, Florida, the morning after they're filed. Job value, contractor and trade on every permit. AI agents pay per search with x402.

## Output

A JSON object with a 'permit' field containing jurisdiction, permit number, address, city, zip, status, record type, description, applied date, issued date, valuation, contractor name, contractor license, contractor key, and an array of trades; plus a 'history' array of every recorded status change with timestamps and valuations.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "properties": {
   "type": "string"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "permit": {
   "zip": "33607",
   "city": "TAMPA",
   "status": "Issued",
   "trades": [
    "roofing"
   ],
   "address": "100 EXAMPLE ST",
   "valuation": 14500,
   "permit_key": "tampa:BLD-26-0000001",
   "description": "Re-roof, shingle",
   "issued_date": "2026-10-16",
   "record_type": "Residential Roofing",
   "applied_date": "2026-10-15",
   "jurisdiction": "City of Tampa",
   "permit_number": "BLD-26-0000001",
   "contractor_key": "ccc0000000",
   "contractor_name": "EXAMPLE ROOFING LLC",
   "contractor_license": "CCC0000000"
  },
  "history": [
   {
    "status": "Issued",
    "seen_at": "2026-10-16T10:30:00Z",
    "valuation": 14500,
    "issued_date": "2026-10-16"
   }
  ]
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/permit-scouter-single-permit-detail-lookup-0980294a/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.permitscouter.com](https://www.zero.xyz/host/api.permitscouter.com/llms.txt)