Montgomery County, MD Permits (data.montgomerycountymd.gov) · Search permits
data-montgomerycountymd-gov/building-permits/search_permitsSearch property, job and marketplace listings with Montgomery County, MD Permits (data.montgomerycountymd.gov) · Search permits from Alexandria through one Spiral API key. Permit history at an address, new houses, decks or pools in a ZIP or community, large commercial or multifamily projects, solar or generator work by description. To monitor for new and changed permits, pass updated_since (the largest updated_at you have seen) with sort updated_desc, once per kind. It runs in the background and returns structured JSON. Pay as you go, with no subscription.
Pricing
$0.00873 per call.
Limits
- Runs
- In the background
- Returns
- json
- 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 | Default | Description |
|---|---|---|---|
zip | text | — | 5-digit ZIP code of the site. Pattern: ^[0-9]{5}$. |
city | text | — | Mailing community, case-insensitive substring (Bethesda, Silver Spring, Takoma Park, Germantown). |
kind | one of residential, commercial, fence, sign, historic_area_work | residential | Which DPS dataset: residential (Residential Permit m88u-pqki: houses, townhouses, additions, decks, sheds, pools, alterations; default), commercial (Commercial Permits i26v-w6bd: commercial and multifamily buildings, tenant fit-outs, change of use), fence (Fence Permits 9quz-avmj), sign (Sign Permits piic-h4rw) or historic_area_work (Historic Area Work Permits bhqn-3agh: exterior work on Master Plan historic sites and districts). |
sort | one of issued_desc, applied_desc, updated_desc, valuation_desc | issued_desc | issued_desc: newest issue date first, unissued applications last; applied_desc: newest application first; updated_desc: most recently added or changed first (for polling); valuation_desc: largest declared valuation first (residential and commercial). |
limit | number 1 to 100 | 25 | Rows per page. |
cursor | text | — | next_cursor from the previous page; repeat the same filters with it. Pattern: ^[0-9]+$. |
status | text | — | Case-insensitive substring of status: open (applied, not yet issued), issued, finaled, stop work. |
address | text | — | Site address words in order, case-insensitive, matched as a substring of '<number> <street> <suffix> <community> MD <ZIP>': 7420 Cedar Ave, 8787 Georgia Ave Silver Spring, cedar ave takoma park. Long suffixes become the abbreviations DPS uses (Avenue AVE, Road RD, Drive DR, Court CT); leave out unit numbers. |
description | text | — | Case-insensitive substring of the published work description: solar, accessory dwelling, generator, elevator. |
permit_type | text | — | Case-insensitive substring over application type, use code and work type: single family, townhouse, deck, pool, shed, multifamily, restaurant, construct (new buildings), add, alter, demolish. |
issued_since | text | — | Only permits issued on or after this day, YYYY-MM-DD. Pattern: ^[0-9]{4}-[0-9]{2}-[0-9]{2}$. |
issued_until | text | — | Only permits issued on or before this day, YYYY-MM-DD. Pattern: ^[0-9]{4}-[0-9]{2}-[0-9]{2}$. |
applied_since | text | — | Only applications added on or after this day, YYYY-MM-DD. Pattern: ^[0-9]{4}-[0-9]{2}-[0-9]{2}$. |
applied_until | text | — | Only applications added on or before this day, YYYY-MM-DD. Pattern: ^[0-9]{4}-[0-9]{2}-[0-9]{2}$. |
min_valuation | number 0 to … | — | Only permits whose declared valuation is at least this many USD. Residential and commercial only; other kinds publish no valuation (invalid_input). |
updated_since | text | — | YYYY-MM-DD (from 00:00 UTC) or an RFC 3339 timestamp: only rows Socrata added or changed at or after it (:updated_at, each record's updated_at). New applications and status changes such as issue or final update a row; DPS loads changes daily. Pattern: ^[0-9]{4}-[0-9]{2}-[0-9]{2}([Tt ][0-9]{2}:[0-9]{2}:[0-9]{2}(\.[0-9]{1,9})?([Zz]|[+-][0-9]{2}:[0-9]{2}))?$. |
Same request in code
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-montgomerycountymd-gov/building-permits/search_permits",
"input": {
"zip": "<zip>"
}
}'Frequently asked questions
How much does Montgomery County, MD Permits (data.montgomerycountymd.gov) · 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 Montgomery County, MD Permits (data.montgomerycountymd.gov) · Search permits through an API?
Send `POST /v1/runs` with `"provider": "alexandria"`, `"model": "data-montgomerycountymd-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 Montgomery County, MD Permits (data.montgomerycountymd.gov) · Search permits?
No. Spiral runs it on its own Alexandria account and charges your Spiral balance.
Can my AI agent use Montgomery County, MD Permits (data.montgomerycountymd.gov) · Search permits?
Yes. Agents find and run it through Spiral's MCP server, CLI or agent skill, with the same API key.