# City of Seattle Open Data: permits and land use decisions · Search permits

Get places and reviews from maps with City of Seattle Open Data: permits and land use decisions · Search permits from Alexandria through one Spiral API key. Permit history at an address, a contractor's jobs, new permits or land use decisions since a date, large projects above a value. For one permit's full row use get_permit; for contractor rankings use contractor_activity. It runs in the background and returns structured JSON. Pay as you go, with no subscription.

- Provider: Alexandria
- Category: Maps & Reviews
- Runs: In the background
- Returns: json
- Tool id: `alexandria` / `data-seattle-gov/building-permits/search_permits`
- Page: https://spiral.ai/tools/alexandria/data-seattle-gov/building-permits/search_permits

## Pricing

$0.00873 per call.

## Limits

- Longest queue wait: 1 hour
- Run deadline: 5 minutes
- Longest run, end to end: 225 minutes
- Largest inline input: 1 MB
- Largest input file: 2 GB
- Largest output: 5 GB

## Input

| Field | Kind | Allowed | Default | Description |
| --- | --- | --- | --- | --- |
| `zip` | text |  | — | Five-digit site ZIP code, for example 98103. Pattern: ^[0-9]{5}$. |
| `kind` | one of | building, trade, electrical, land_use | building | Which SDCI dataset: building (Building Permits 76t5-zqzr: construction, additions, demolition, grading, roofing, shoreline and critical-area exemptions), trade (Trade Permits c87v-5hwh: mechanical, furnace, refrigeration, elevator, boiler, sign and fire sprinkler), electrical (Electrical Permits c4tj-daue) or land_use (Land Use Permits ht3q-kdvx: master use permits, design review and early design guidance, the land use decisions that precede building permits). |
| `sort` | one of | issued_desc, applied_desc, decided_desc, valuation_desc | — | Order, newest or largest first, missing values last. Defaults to issued_desc, or applied_desc when only application dates are filtered, or decided_desc (land_use only) when decision dates are filtered. |
| `limit` | number | 1 to 100 | 25 | Records per page. |
| `cursor` | text |  | — | The next_cursor of the previous page. Pattern: ^[0-9]{1,7}$. |
| `status` | text |  | — | Words matched against the current status, for example Issued, Completed, Reviews In Process, Published. |
| `address` | text |  | — | Site address words, case-insensitive, matched in order as a substring: 400 Broad St, 1959 NE Pacific. Use Seattle's abbreviations (ST, AVE, NE). |
| `contractor` | text |  | — | Contractor company words, case-insensitive substring, for example Greenwood Heating. |
| `description` | text |  | — | Words matched in order against the work description, for example ADU, solar, heat pump, demolish. |
| `permit_type` | text |  | — | Words matched against the permit type, class and work type, for example New, Demolition, Multifamily, Fire Sprinkler, Design Review. |
| `issued_since` | text |  | — | First issue date, inclusive (YYYY-MM-DD). Poll for newly issued permits with this and sort issued_desc. Pattern: ^[0-9]{4}-[0-9]{2}-[0-9]{2}$. |
| `issued_until` | text |  | — | Last issue date, inclusive (YYYY-MM-DD). Pattern: ^[0-9]{4}-[0-9]{2}-[0-9]{2}$. |
| `applied_since` | text |  | — | First application date, inclusive (YYYY-MM-DD). Poll for new applications with this; without issue-date filters the default sort becomes applied_desc. Pattern: ^[0-9]{4}-[0-9]{2}-[0-9]{2}$. |
| `applied_until` | text |  | — | Last application date, inclusive (YYYY-MM-DD). Pattern: ^[0-9]{4}-[0-9]{2}-[0-9]{2}$. |
| `decided_since` | text |  | — | First land use decision date, inclusive (YYYY-MM-DD). Kind land_use only; the default sort becomes decided_desc. Pattern: ^[0-9]{4}-[0-9]{2}-[0-9]{2}$. |
| `decided_until` | text |  | — | Last land use decision date, inclusive (YYYY-MM-DD). Pattern: ^[0-9]{4}-[0-9]{2}-[0-9]{2}$. |
| `min_valuation` | number | 0 to … | — | Only permits whose estimated project cost is at least this many US dollars. |
| `related_land_use_permit` | text |  | — | Building permits that implement this land use permit (the relatedmup column), for example 3018806-LU. Kind building only. Pattern: ^[0-9]{7}-[A-Za-z]{2}(-[0-9]{3})?$. |

## Example

```bash
curl https://api.spiral.ai/v1/runs \
  -H "Authorization: Bearer $SPIRAL_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: $(uuidgen)" \
  -d '{
    "provider": "alexandria",
    "model": "data-seattle-gov/building-permits/search_permits",
    "input": {
      "zip": "<zip>"
    }
  }'
```

Try it in the Playground: https://spiral.ai/start?provider=alexandria&model=data-seattle-gov%2Fbuilding-permits%2Fsearch_permits

## Common questions

### City of Seattle Open Data: permits and land use decisions · Search permits

**How much does City of Seattle Open Data: permits and land use decisions · Search permits cost?**

$0.00873 per call. You pay as you go from one Spiral balance, with no subscription, and a failed run is not charged.

**How do I use City of Seattle Open Data: permits and land use decisions · Search permits through an API?**

Send `POST /v1/runs` with `"provider": "alexandria"`, `"model": "data-seattle-gov/building-permits/search_permits"` and the input fields on this page, using one Spiral API key. It runs in the background: poll the run, or name a webhook to be told when it finishes.

**Do I need an account with Alexandria to use City of Seattle Open Data: permits and land use decisions · Search permits?**

No. Spiral runs it on its own Alexandria account and charges your Spiral balance.

**Can my AI agent use City of Seattle Open Data: permits and land use decisions · Search permits?**

Yes. Agents find and run it through Spiral's MCP server, CLI or agent skill, with the same API key.

