ToolVet
77trust / 100

Sold Prices

by property.payapi.market in Markets & finance

x402 APIPassing, checked 1 h ago

UK HM Land Registry sold property prices by postcode.

POST https://property.payapi.market/sold-prices

Last 30 days

All checks passedSome failedAll failedNot checked

Status and outage history · Atom feed

Uptime
100%
Response time
502 ms typical, 758 ms slowest 5%
Last check
1 h ago
Next check
any minute now

How to call it

POST https://property.payapi.market/sold-prices

Each call costs $0.001 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.

POST https://property.payapi.market/sold-prices
content-type: application/json

{
  "limit": 10,
  "postcode": "SW1A 1AA"
}

Parameters

ParameterTypeRequiredDescription
limitintegerNoMax records to return. Defaults to 10.
postcodestringYesUK postcode to search, e.g. 'SW1A 1AA'.

Example response

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

{
  "cached": false,
  "count": 2,
  "postcode": "SW1A 1AA",
  "results": [
    {
      "address": "10 DOWNING STREET, LONDON",
      "date": "2024-06-14",
      "new_build": false,
      "price": 2750000,
      "property_type": "T"
    },
    {
      "address": "12 DOWNING STREET, LONDON",
      "date": "2023-11-02",
      "new_build": false,
      "price": 1900000,
      "property_type": "T"
    }
  ]
}

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.001.

curl: see the payment challenge
# bash or zsh: see the payment challenge. Nothing is charged.
curl -sS -g -i -X POST 'https://property.payapi.market/sold-prices' \
  -H 'content-type: application/json' \
  --data-raw '{"limit":10,"postcode":"SW1A 1AA"}'

# 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 - -X POST 'https://property.payapi.market/sold-prices' \
  -H 'content-type: application/json' \
  --data-raw '{"limit":10,"postcode":"SW1A 1AA"}' \
  | 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.001 per call.
const client = new x402Client().setSpendControls({ maxAmountPerPayment: "$0.001" });
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.001 per payment. GET https://toolvet.app/api/v1/check?url=https%3A%2F%2Fproperty.payapi.market%2Fsold-prices&method=POST
const res = await pay("https://property.payapi.market/sold-prices", {
  method: "POST",
  headers: { "content-type": "application/json" },
  body: JSON.stringify({
    "limit": 10,
    "postcode": "SW1A 1AA"
  }),
});
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.001 per call.
client = x402ClientSync().set_spend_controls({"max_amount_per_payment": "$0.001"})
register_exact_evm_client(client, EthAccountSigner(Account.from_key(os.environ["EVM_PRIVATE_KEY"])))

with x402_requests(client) as session:
    res = session.post(
        "https://property.payapi.market/sold-prices",
        json={
            "limit": 10,
            "postcode": "SW1A 1AA",
        },
    )
    print(res.status_code, res.text)

Security scan

  • No findings. We scan names, descriptions and tool definitions for hidden instructions and other prompt-injection patterns.

Recent checks

WhenResultHTTPTimePrice
1 h agoPassed402453 ms$0.001
5 h agoPassed402607 ms$0.001
9 h agoPassed402526 ms$0.001
13 h agoPassed402463 ms$0.001
17 h agoPassed402607 ms$0.001
21 h agoPassed402593 ms$0.001
25 h agoPassed402478 ms$0.001
29 h agoPassed402478 ms$0.001
33 h agoPassed402566 ms$0.001
36 h agoPassed402423 ms$0.001
40 h agoPassed402496 ms$0.001
43 h agoPassed402571 ms$0.001
47 h agoPassed402476 ms$0.001
2 days agoPassed402763 ms$0.001
2 days agoPassed402494 ms$0.001