Nosy Neighbor for developers

Programmatic access to the same NYC property data the web app shows: the five boroughs only (Manhattan, Brooklyn, Queens, the Bronx, Staten Island), nothing else. Both surfaces bill against ONE account allowance:

Which one do I want?

• Building an app, script, or backend integration? Use the REST API. Mint a key from the developer dashboard and start with the quickstart.
• Using an AI agent (Claude, or another MCP client)? Use MCP. See setup for tested client configs.
• Calling it from code you are writing by hand, and want retries, SDKs, or typed responses? REST is the more conventional fit. The interactive API reference documents every field.

What is covered

The same operations run on either surface. Each one has an MCP tool name and a REST path, so the property report is lookup_property to an agent and /v1/lookup over HTTP.

• A full property report for one address.
• Listing search across an area.
• Comparable sold homes.
• Rental estimates.
• A digest of listings that changed.
• Current mortgage rates.

Every one of them enforces NYC-only coverage: an address, ZIP, or area outside the five boroughs gets a short coverage message, never a partial or best-effort answer, on both surfaces.

One shared allowance

The REST API and MCP are not separately metered: a call through either counts against the same per-minute and per-day allowance on your account. See Rate Limits for the exact numbers and per-operation costs.