What Borough provides
- Dozens of structured listing fields across summary and detail endpoints, including pricing, concessions, amenities, photos, and freshness metadata
- Building-level data with amenities, policies, NYC regulatory data, and quality scores
- First-party photo delivery through
/v1/photos/{key}for supported Borough image sizes - Likely internet providers with FCC-sourced provider names, technologies, and advertised speeds
- 349 neighborhoods with encoded map boundaries
- Market snapshots with inventory, median prices, days on market, and concession rates
- Building quality scores derived from NYC Open Data (HPD violations, 311 noise, NYPD crime, transit proximity)
- Live SSE streaming for instant cached + live listing data (Pro+)
- Persistent watchers that monitor listings, buildings, or searches for changes (Business+)
- Webhooks for automated notifications on price drops, new listings, and status changes (Business+)
- MCP server for connecting AI agents directly to NYC real estate data
Pricing
| Tier | Price | Requests/month | Rate Limit |
|---|---|---|---|
| Free | $0 | 100 | 10/min |
| Starter | $19/mo | 5,000 | 30/min |
| Pro | $49/mo | 25,000 | 60/min |
| Business | $99/mo | 100,000 | 120/min |
/v1/health endpoint is also available without authentication, but it is outside Borough’s metered /v1 data surface. Starter and above unlock property details and building data. Pro adds live SSE streaming. Business adds webhooks, persistent watchers, and change notifications.
Product surface
Borough keeps its public product pages and service runtime on the same hostname without changing the integration URLs developers depend on.- Public site and legal pages live at
borough.qwady.app/ - REST endpoints stay under
borough.qwady.app/v1/* - MCP remains at
borough.qwady.app/mcp - OAuth and discovery stay under
borough.qwady.app/oauth/*andborough.qwady.app/.well-known/* - Webhook subscriptions stay under
borough.qwady.app/v1/webhooks/*
Internet provider availability
Building and property detail responses can include aninternetProviders block sourced from official FCC Broadband Data Collection public data.
- Coverage is exact-building when Borough has a matched FCC location and Census-block level when sourced from FCC public bulk files
- Coverage is not unit-specific qualification
- Data reflects likely providers, advertised technologies, and max download/upload speeds
- Borough refreshes broadband availability on a monthly cadence and supports manual backfills for operational re-syncs
This product uses FCC APIs and/or Data but is not endorsed or certified by the FCC.
Quickstart
Get your API key and make your first request in under 2 minutes
API Reference
Explore all 20+ endpoints with examples and response schemas
MCP Server
Connect Claude, Cursor, or VS Code to query NYC data via AI
TypeScript SDK
Install the official SDK for typed access with auto-pagination