80trust / 100

Nyc Property Check

by NYC HPD Violations Address in Developer tools

x402 APIPassing, checked 16 min ago

NYC HPD violations address check: is this property licensed / HPD-registered, and are there open Housing Maintenance Code violations? Property due diligence agent for New York City multi-dwelling housing compliance open data. GET ?address= (house + street, optional borough) → registration window, BIN/block/lot, recent HMC violations JSON. Tenant screening, landlord DD.

GET
https://x402-mcp.onrender.com/us/nyc/property-check
Price
$0.01
per call in USDC
Uptime
100%
last 30 days
Response time
232 ms
665 ms slowest 5%
Last check
Passed
16 min ago, next in 16 min

Run a free test callHow to call it

Reliability

All checks passedSome failedAll failedNot checked

Status and outage history · Atom feed · Watch with other listings

How to call it

GET https://x402-mcp.onrender.com/us/nyc/property-check

Each call costs $0.01 in USDC on Base, paid with the request over x402.

Run a free test callOne unpaid request, the way an agent sends it. You see the payment challenge it gets back. Nothing is charged.

Example request

From the listing.

GET https://x402-mcp.onrender.com/us/nyc/property-check?address=787+EAST+56+STREET+BROOKLYN

Example response

The provider's example. We can't check it without paying.

{
  "address_queried": "787 EAST 56 STREET BROOKLYN",
  "city": "nyc",
  "city_name": "New York City",
  "compliance_verdict": "registered_clean",
  "registered": true,
  "registrations": [
    {
      "borough": "BROOKLYN",
      "house_number": "787",
      "registration_end_date": "2026-09-01T00:00:00.000",
      "registration_id": "825850",
      "street": "EAST 56 STREET"
    }
  ],
  "state": "NY",
  "violation_cases": {
    "recent": [],
    "total": 0
  }
}

Call it from code

The curl command shows the payment challenge. The JavaScript and Python versions pay and call, and never pay more than $0.01.

curl: see the payment challenge
# bash or zsh: see the payment challenge. Nothing is charged.
curl -sS -g -i 'https://x402-mcp.onrender.com/us/nyc/property-check?address=787+EAST+56+STREET+BROOKLYN'

# x402 v2 sends the challenge base64-encoded in the PAYMENT-REQUIRED header (v1 sends it in the body).
# To read the header:
curl -sS -g -o /dev/null -D - 'https://x402-mcp.onrender.com/us/nyc/property-check?address=787+EAST+56+STREET+BROOKLYN' \
  | grep -i '^payment-required:' | cut -d' ' -f2 | tr -d '\r' | base64 --decode
JavaScript: pay and call
// npm i @x402/fetch @x402/evm viem
import { wrapFetchWithPayment, x402Client } from "@x402/fetch";
import { registerExactEvmScheme } from "@x402/evm/exact/client";
import { privateKeyToAccount } from "viem/accounts";

// Pays at most $0.01 per call.
const client = new x402Client().setSpendControls({ maxAmountPerPayment: "$0.01" });
registerExactEvmScheme(client, { signer: privateKeyToAccount(process.env.EVM_PRIVATE_KEY) });
const pay = wrapFetchWithPayment(fetch, client);

// Not sure it's safe to pay? ToolVet checks it first for $0.005. Pay for that from a separate
// client: this one is capped at $0.01 per payment. GET https://toolvet.app/api/v1/check?url=https%3A%2F%2Fx402-mcp.onrender.com%2Fus%2Fnyc%2Fproperty-check
const res = await pay("https://x402-mcp.onrender.com/us/nyc/property-check?address=787+EAST+56+STREET+BROOKLYN");
console.log(res.status, await res.text());
Python: pay and call
# pip install "x402[requests,evm]"
import os
from eth_account import Account
from x402 import x402ClientSync
from x402.http.clients import x402_requests
from x402.mechanisms.evm import EthAccountSigner
from x402.mechanisms.evm.exact.register import register_exact_evm_client

# Pays at most $0.01 per call.
client = x402ClientSync().set_spend_controls({"max_amount_per_payment": "$0.01"})
register_exact_evm_client(client, EthAccountSigner(Account.from_key(os.environ["EVM_PRIVATE_KEY"])))

with x402_requests(client) as session:
    res = session.get("https://x402-mcp.onrender.com/us/nyc/property-check?address=787+EAST+56+STREET+BROOKLYN")
    print(res.status_code, res.text)

Security scan

1 finding

  • Payment address changed recently in payment
    Payment address changed from 0x05e1720bB82F86B5bc7940a99FDC702E32256357 to 0x0d25A44f74868eCE53B305C97139CF4B62963410

Recent checks

WhenResultHTTPTimePrice
16 min agoPassed402208 ms$0.01
4 h agoPassed402231 ms$0.01
8 h agoPassed402237 ms$0.01
12 h agoPassed402372 ms$0.01
16 h agoPassed402221 ms$0.01
Show 10 older checks
19 h agoPassed402201 ms$0.01
22 h agoPassed402260 ms$0.01
25 h agoPassed402568 ms$0.01
28 h agoPassed402201 ms$0.01
31 h agoPassed402232 ms$0.01
34 h agoPassed402244 ms$0.01
38 h agoPassed402200 ms$0.01
43 h agoPassed402255 ms$0.01
2 days agoPassed402573 ms$0.01
2 days agoPassed402211 ms$0.01

History

17 Oct 2026Payment address changed from 0x05e1720bB82F86B5bc7940a99FDC702E32256357 to 0x0d25A44f74868eCE53B305C97139CF4B62963410