80trust / 100

Phi Property Check

by Philly L&I Violations in Weather & location

x402 APIPassing, checked 16 min ago

Does this Philadelphia address have open L&I property maintenance violations? Query a street address and get violation codes, status, case numbers, and dates from OpenDataPhilly. For tenant screening and landlord diligence. Input: address string. Output: JSON, live City of Philadelphia open data.

GET
https://x402-mcp.onrender.com/us/phi/property-check
Price
$0.01
per call in USDC
Uptime
100%
last 30 days
Response time
252 ms
771 ms slowest 5%
Last check
Passed
16 min ago, next in 17 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/phi/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/phi/property-check?address=1234+N+LEITHGOW+ST

Example response

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

{
  "address_queried": "1234 N LEITHGOW ST",
  "city": "phi",
  "city_name": "Philadelphia",
  "compliance_verdict": "violations_open",
  "registered": false,
  "registrations": [],
  "state": "PA",
  "violation_cases": {
    "open_count": 1,
    "recent": [
      {
        "address": "1234 N LEITHGOW ST",
        "case_number": "CF-2026-073975",
        "code": "PM15-302.4",
        "status": "OPEN"
      }
    ],
    "total": 1
  }
}

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/phi/property-check?address=1234+N+LEITHGOW+ST'

# 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/phi/property-check?address=1234+N+LEITHGOW+ST' \
  | 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%2Fphi%2Fproperty-check
const res = await pay("https://x402-mcp.onrender.com/us/phi/property-check?address=1234+N+LEITHGOW+ST");
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/phi/property-check?address=1234+N+LEITHGOW+ST")
    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 agoPassed402647 ms$0.01
4 h agoPassed402214 ms$0.01
8 h agoPassed402771 ms$0.01
12 h agoPassed402308 ms$0.01
16 h agoPassed402233 ms$0.01
Show 10 older checks
19 h agoPassed402281 ms$0.01
22 h agoPassed402621 ms$0.01
25 h agoPassed402673 ms$0.01
28 h agoPassed402661 ms$0.01
31 h agoPassed402599 ms$0.01
34 h agoPassed402240 ms$0.01
38 h agoPassed402238 ms$0.01
43 h agoPassed402194 ms$0.01
2 days agoPassed402203 ms$0.01
2 days agoPassed402211 ms$0.01

History

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