property.nyc-permits

NYC Department of Buildings permit issuance — every construction, alteration, or demolition permit ever issued. Search by `bbl` (10-digit) or `address` (street_name substring). Filter by jobType (A1=Major Alteration, A2=Minor Alteration, A3=Minor Cosmetic, NB=New Building, DM=Demolition, etc.) or permitStatus (ISSUED, IN PROCESS, RE-ISSUED, REVOKED, etc.). Each row carries job + permit numbers, work type, building type, residential flag, filing/issuance/expiration dates, estimated fee. Use for construction-history agents, code-enforcement research, and zoning compliance checks.

price
$0.0012 USDC per call
method
GET/api/property/nyc-permits
payment
x402 v2 · USDC on Base (EIP-3009) or Solana (SPL transfer)
auth
None. Sign the payment, retry with PAYMENT-SIGNATURE.

Overview

The nyc permits API is a pay-per-call property endpoint built for AI agents and autonomous software. NYC Department of Buildings permit issuance — every construction, alteration, or demolition permit ever issued.

There is no signup and no API key. An agent (or any HTTP client) hits the endpoint, receives an x402 "402 Payment Required" challenge, signs a sub-cent USDC payment on Base or Solana, and retries — the data comes back on the paid request. That makes it a drop-in nyc permits data source for an agent tool-use loop, an MCP host, or a backend that needs property data on demand without onboarding to yet another vendor portal.

Use cases

Parameters

NameTypeDescription
bblstring
match ^[1-5][- 0-9]{9,19}$
addressstring
min 3 chars · max 120 chars
jobTypestring
match ^[A-Za-z0-9]{1,5}$
permitStatusstring
match ^[A-Za-z _-]{2,30}$
limitinteger
min 1 · max 200
offsetinteger
min 0

Code samples

cURLbash
# 1. Probe with no auth → 402 envelope with PaymentRequirements
curl -sS 'https://2s.io/api/property/nyc-permits?bbl=example&address=xxx&jobType=example&permitStatus=example&limit=25&offset=0'

# 2. Sign + retry with PAYMENT-SIGNATURE:
curl -sS 'https://2s.io/api/property/nyc-permits?bbl=example&address=xxx&jobType=example&permitStatus=example&limit=25&offset=0' \
  -H 'PAYMENT-SIGNATURE: <base64-json-payload>'

# Or use the canonical runner (handles probe → sign → retry):
#   EVM_PRIVATE_KEY=0x... node --env-file=.env.local \
#     --experimental-strip-types scripts/x402-pay.ts \
#     'https://2s.io/api/property/nyc-permits?bbl=example&address=xxx&jobType=example&permitStatus=example&limit=25&offset=0'
TypeScript / Node — @2sio/sdktypescript
import { TwoS } from '@2sio/sdk'

const client = new TwoS({
  privateKey: process.env.EVM_PRIVATE_KEY as `0x${string}`,
})

const result = await client.property.nycPermits({
  "bbl": "example",
  "address": "xxx",
  "jobType": "example",
  "permitStatus": "example",
  "limit": 25,
  "offset": 0
})

console.log('endpoint:', result.endpoint)
console.log('cost:', result.costUsd, 'USDC')
console.log('tx:', result.settlement?.txHash)
console.log('data:', result.data)
Python — 2siopython
import os
from twosio import TwoS

client = TwoS(private_key=os.environ["EVM_PRIVATE_KEY"])

result = client.property.nyc_permits(bbl="example", address="xxx", jobType="example", permitStatus="example", limit=25, offset=0)

print("endpoint:", result.endpoint)
print("cost:", result.cost_usd, "USDC")
print("tx:", (result.settlement or {}).get("tx_hash"))
print("data:", result.data)
MCP — Claude Desktop / AgentKit / any MCP hostjson
// 1. Add @2sio/mcp to your MCP host config (Claude Desktop example below).
//    EVM_PRIVATE_KEY funds x402 payments per call.

// claude_desktop_config.json
{
  "mcpServers": {
    "2sio": {
      "command": "npx",
      "args": ["-y", "@2sio/mcp"],
      "env": { "EVM_PRIVATE_KEY": "0x..." }
    }
  }
}

// 2. Once the server is running, agents call this tool via standard MCP:

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "property.nyc-permits",
    "arguments": {
      "bbl": "example",
      "address": "xxx",
      "jobType": "example",
      "permitStatus": "example",
      "limit": 25,
      "offset": 0
    }
  }
}

Response

FieldTypeDescription
okboolean
one of: true
itemsarray
totalintegerTotal matching rows upstream; null when unknown.
sourceobject
Example response datajson
{
  "ok": true,
  "items": [
    {}
  ],
  "total": 1,
  "source": {
    "provider": "example",
    "url": "example",
    "license": "example"
  }
}

FAQ

Do I need an API key to use the nyc permits API?
No. property.nyc-permits is x402-native — there is no signup and no API key. Your client makes the call, receives a 402 with payment requirements, signs a USDC payment, and retries. Funds come from a wallet you control.
How much does the nyc permits API cost?
$0.0012 USDC per call, charged per request. There are no monthly fees, seats, or minimums — you pay only for the calls you make.
Can I try the nyc permits API for free first?
Yes. Add ?trial=1 (or the header X-2s-Trial: 1) to get a free real call per endpoint per hour, so you can verify the response shape before wiring payment.
Which networks and tokens are supported?
USDC on Base (via EIP-3009 transferWithAuthorization) or Solana (SPL transfer), using the open x402 payment protocol.
How do I call property.nyc-permits from an AI agent or MCP host?
Use @2sio/sdk (TypeScript), 2sio (Python), or the @2sio/mcp server for any MCP host — each handles the probe → sign → retry loop for you. See the code samples on this page.

Discovery

Related: nyc permits api · property nyc permits api · nyc permits api for ai agents · x402 property api · nyc permits api no api key · pay per call nyc permits api · property api