Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we
store it to create your key and to recognise you if you sign in with another
provider. By signing up you are subscribing to the APIs.io and API Evangelist
newsletters — you can unsubscribe from any issue. See our
Privacy Policy and Terms.
openapi: 3.2.0
info:
title: Nearby Permits Address API
version: 0.1.0
description: 'Building permits by address from US city open data. The API is free and read-only. The JSON API needs a free key from https://nearbypermits.com/developers/#key. Each key gets 10,000 calls a day; send it as "Authorization: Bearer " or add ?key= to the URL. Search engines and AI answer bots that we can check against their published IP addresses need no key and have no limit. The MCP server needs no key: each IP address gets 200 tool calls a day, or 10,000 with a key sent as an Authorization header. A JSON API call without a key is refused. Over the limit, the API answers 429 with a JSON body and a Link header to https://nearbypermits.com/developers/#key. Counts start again at midnight UTC.'
servers:
- url: https://nearbypermits.com
security:
- bearerKey: []
- queryKey: []
tags:
- name: Address
paths:
/v1/address:
get:
operationId: permitsAtAddress
summary: Permits at a street address, newest first (at most 200)
parameters:
- name: city
in: query
required: true
schema:
type: string
enum:
- los-angeles
- new-york
- chicago
- san-francisco
- seattle
- austin
- cincinnati
- mesa
- new-orleans
- fort-worth
- columbus
- san-diego
- detroit
- nashville
- raleigh
- phoenix
- san-antonio
- minneapolis
- montgomery-county-md
- boston
- pittsburgh
- washington-dc
- denver
- los-angeles-county
- wake-county
- miami
- miami-dade-county
- hillsborough-county
- cape-coral
- port-st-lucie
- alachua-county
- kansas-city
- baltimore
- sacramento-county
- memphis
- las-vegas
- tacoma
- boulder
- cambridge
- somerville
- marin-county
- pierce-county
- cary
- cleveland
- arlington-tx
- naperville
- tempe
- anaheim
- riverside
- name: address
in: query
required: true
schema:
type: string
maxLength: 120
example: 867 N Iliff St
responses:
'200':
description: 'Permits, an answer to quote, a story ({kind, text} or null: one sentence about the block, also the first sentence of the answer) and a page URL to cite. /v1/address and the MCP tool permits_at_address list the permits at one address, newest first, at most 200. count is how many are listed. When capped is true the city holds more, and total is the city''s own count, or null if the count didn''t come back in time. history_limited means the city''s portal didn''t answer, so the list is our copy only. A loosely typed address (missing N or S, a spelled-out street word, a trailing city, state or ZIP, a unit) is matched to the spelling the city files; typed_address then holds what was sent. When more than one address matches, did_you_mean lists them (address, permits: recent permits in our copy, page) and count is 0.'
'400':
description: Bad input
'401':
description: The key is missing or isn't valid. The body says where to get a free key.
'403':
description: No key was sent.
'429':
description: This key reached its daily limit. The body says how to ask for a higher one, and Retry-After gives the seconds to midnight UTC.
tags:
- Address
components:
securitySchemes:
bearerKey:
type: http
scheme: bearer
description: Free key from https://nearbypermits.com/developers/#key
queryKey:
type: apiKey
in: query
name: key