# SiteVerdict — Land Registry Sold Price Alerts (UK) (`siteverdict/siteverdict-land-registry-price-alerts`) Actor

Get alerted to new house sales in your postcodes, streets or towns from HM Land Registry Price Paid Data (OGL). Reads each monthly update, alerts only new sales, adds sector comparables (price vs median) and 12-month area stats. Slack/webhook alerts, CSV. England and Wales.

- **URL**: https://apify.com/siteverdict/siteverdict-land-registry-price-alerts.md
- **Developed by:** [Aman Thakran](https://apify.com/siteverdict) (community)
- **Categories:** Business, Lead generation
- **Features:** Limited permissions
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

Pay per event

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## SiteVerdict — Land Registry Sold Price Alerts (UK)

**Be first to know what houses actually sold for in your patch. Each month HM Land Registry publishes new completions; this Actor reads the official update, alerts you only to sales it has not shown you before, and tells you how each price compares with the local market.**

Official open data: HM Land Registry **Price Paid Data** (Open Government Licence). England and Wales. No key, no portal scraping.

### What you get

- 🏠 **New-sale alerts** for every watched postcode, sector, outcode, street or town: price, completion date, full address, property type, tenure, new-build flag, category, and the official HM Land Registry record link.
- ⚖️ **Comparables pack** per sale: same property type in the same postcode sector over 24 months — median, quartiles, **price vs median %** and the 5 most recent comparable sales.
- 📊 **Watch summaries** (free): sales found in the monthly file, new vs already-seen, plus 12-month area stats (median, quartiles, monthly trend, half-on-half change).
- 🔁 **Never alerted twice**: a named state store remembers what you have seen; amended records (status C) can re-alert; deletions (status D) are reported.
- 🔔 Slack / webhook digests, `new-sales.csv`, optional AI brief with your own key.

### Who it is for

- **Estate agents and lettings agents** prospecting around recent completions and valuing instructions.
- **Investors, sourcers and developers** tracking sold prices on target streets.
- **Surveyors, mortgage brokers and conveyancers** wanting fresh comparables.
- **Local journalists and proptech apps** publishing "what sold this month".
- **AI agents** via the MCP tool `land_registry_alerts`.

### Quick start

1. Watches: `PL4 7`, `Mutley Plain, Plymouth`, `town:Bath`, `district:Cornwall`.
2. Optional filters: property types, tenure, new build, price range.
3. Run once (baseline), then **schedule weekly**: the monthly file is checked cheaply (ETag) and only downloaded when HM Land Registry publishes a new one (usually around the 20th working day of the month).

Try **Sample mode** first (official responses recorded on 11 Oct 2026; no network, free).

#### Example input

```json
{
  "watches": ["PL4 7", "Mutley Plain, Plymouth", "town:Totnes"],
  "propertyTypes": ["T", "S"],
  "maxPrice": 450000,
  "backfillMonths": 3,
  "alertOnFirstRun": true,
  "slackWebhookUrl": "<secret>",
  "stateStoreName": "plymouth-sold-prices"
}
```

#### Example output (sample mode: real HM Land Registry data recorded 11 Oct 2026, abridged)

```json
{ "recordType": "new-sale", "watch": "PL4", "date": "2026-08-21", "price": 235000, "address": "55, CATTEDOWN ROAD, PLYMOUTH, PL4 0PL",
  "propertyTypeLabel": "Terraced", "tenure": "freehold", "newBuild": false, "category": "A",
  "comparables": { "basis": "Terraced sales in postcode sector PL4 0, last 24 months (category A)", "count": 31, "medianPrice": 169950, "p25": 159000, "p75": 191500,
                   "priceVsMedianPct": 38.3, "recent": [{ "date": "2026-07-03", "price": 200000, "address": "49, ALVINGTON STREET, PLYMOUTH, PL4 0QL" }] },
  "linkedDataUri": "https://landregistry.data.gov.uk/data/ppi/transaction/5A7B802C-7A8C-1886-E063-4704A8C021AE/current" }

{ "recordType": "watch-summary", "watch": "PL4", "newSales": 32,
  "areaStats": { "months": 12, "priceStats": { "count": 302, "median": 195000, "p25": 138500, "p75": 234125 }, "halfOnHalfMedianChangePct": -6 } }
```

### Pricing (pay per event)

| Event | Price | When |
|---|---|---|
| `new-sale` | $0.004 | one newly published sale in a watched area |
| `comparables-pack` | $0.006 | comparables (≥ 3 same-type sales in the sector) attached to a new sale |
| `ai-brief` | $0.05 | only when your own AI key returns a brief |

Examples: a postcode sector usually has 5-40 new sales a month → **$0.05-0.40/month** with comparables. A whole town (≈ 300 sales) ≈ $3/month. Baseline runs, summaries, deletions and sample mode are free.

### How it works

- **Monthly update file**: `pp-monthly-update-new-version.csv` (HTTPS from HM Land Registry's public S3 bucket) contains every record added (A), changed (C) or deleted (D) in the latest publication. One download serves all your watches. A HEAD request with the stored ETag skips unchanged files.
- **Report builder** (`landregistry.data.gov.uk/app/ppd`) is used for comparables, 12-month area stats, first-run backfill and as a fallback if the monthly file is unavailable. Requests are spaced 0.7 s apart.
- Category B sales (repossessions, buy-to-let, company sales) are off by default.

### FAQ

**Why didn't a sale I know about appear?** HM Land Registry publishes Price Paid Data once a month (around the 20th working day). A sale usually appears 2 weeks to 2 months after completion, and later when registration is delayed, so alerts are never real-time. Some transfers are excluded (e.g. non-market-value, most commercial).

**Can I watch a radius around a point?** Use the postcode sector or outcode; points are not supported for alerts.

**Who owns the house?** Price Paid Data contains no owner names and we never add any.

### Limits

- England and Wales only (Scotland: Registers of Scotland; NI: LPS).
- 200 watches per run; up to 20,000 remembered sales per watch.
- Comparables lookups are capped at 50 sectors per run.
- If a run reaches your **max total charge** (or the 5,000-alert cap per run), the remaining sales are **not charged and not marked as seen**: they are listed in OUTPUT (`incomplete`, `deferredSales`, `deferred`) and in the run status ("N sale(s) deferred to next run"), and arrive on the next run. A budget used up exactly with nothing left over is a normal, complete run.

### Sources & compliance

- **Source**: HM Land Registry Price Paid Data — monthly update file and report builder. Guidance: https://www.gov.uk/guidance/about-the-price-paid-data (checked 11 Oct 2026). robots.txt allows `/app/ppd/ppd_data.csv`.
- **Licence**: Open Government Licence v3.0. Attribution on every run: *Contains HM Land Registry data © Crown copyright and database right 2021. This data is licensed under the Open Government Licence v3.0.*
- **Address data notice**: Price Paid address fields are processed against Ordnance Survey AddressBase Premium (incorporating Royal Mail PAF). Royal Mail and OS permit their use for personal and/or non-commercial use and for providing residential property price information services; **other uses (e.g. direct marketing lists) need a Royal Mail licence**.
- **Personal data / UK GDPR & PECR**: addresses of sold homes can relate to identifiable people. Use alerts for market analysis and valuation; do not use them to build unsolicited marketing lists (PECR) without the right licences and a lawful basis.
- Honest user agent `SiteVerdict/land-registry-price-alerts (+hello@webrevenuescan.com)`. **Not valuation, legal or financial advice.**

# Changelog

This Actor's version history is a separate document: https://apify.com/siteverdict/siteverdict-land-registry-price-alerts/changelog.md

# Actor input Schema

## `watches` (type: `array`):

One per line: full postcode <code>PL4 7LG</code>, sector <code>PL4 7</code>, outcode <code>PL4</code>, street <code>Mutley Plain, Plymouth</code>, or <code>town:Bath</code> / <code>district:Cornwall</code> / <code>county:Devon</code> / <code>locality:NAME</code>. Max 200.

## `propertyTypes` (type: `array`):

Empty = all.

## `tenure` (type: `array`):

Empty = both.

## `newBuild` (type: `string`):

Filter on the HM Land Registry new-build flag.

## `minPrice` (type: `integer`):

Optional minimum price.

## `maxPrice` (type: `integer`):

Optional maximum price.

## `includeCategoryB` (type: `boolean`):

Repossessions, buy-to-lets identified by mortgage, sales to companies, other property types.

## `alertOnFirstRun` (type: `boolean`):

Off: the first run saves the current monthly file as a baseline and alerts start next month. On: everything in the current monthly file is alerted now.

## `backfillMonths` (type: `integer`):

Also pull the last N months from the official report builder when a watch is new (0-24).

## `alertOnChanges` (type: `boolean`):

HM Land Registry sometimes corrects a published sale (record status C). Alert again when that happens.

## `includeComparables` (type: `boolean`):

Same property type in the same postcode sector over 24 months: median, quartiles, price vs median and 5 recent sales.

## `includeAreaStats` (type: `boolean`):

12-month area stats per watch (free)

## `stateStoreName` (type: `string`):

Named key-value store that remembers which sales were already alerted.

## `webhookUrl` (type: `string`):

JSON digest of new sales. Stored encrypted, never logged.

## `slackWebhookUrl` (type: `string`):

https://hooks.slack.com/services/... Stored encrypted, never logged.

## `exportCsv` (type: `boolean`):

Save a CSV export to the run key-value store.

## `aiProvider` (type: `string`):

Optional AI brief written by your own Anthropic or OpenAI account. Off by default.

## `aiApiKey` (type: `string`):

Your own key. Stored encrypted, never logged or output.

## `aiModel` (type: `string`):

Default: claude-sonnet-5-5 (Anthropic) or gpt-4.1-mini (OpenAI).

## `sampleMode` (type: `boolean`):

Replays official responses recorded on 11 Oct 2026 for PL4 / PL6 5 / Mutley Plain. Nothing is charged.

## Actor input object example

```json
{
  "watches": [
    "PL4 7",
    "Mutley Plain, Plymouth"
  ],
  "newBuild": "any",
  "includeCategoryB": false,
  "alertOnFirstRun": false,
  "backfillMonths": 0,
  "alertOnChanges": false,
  "includeComparables": true,
  "includeAreaStats": true,
  "stateStoreName": "siteverdict-lr-alerts",
  "exportCsv": true,
  "aiProvider": "none",
  "sampleMode": false
}
```

# Actor output Schema

## `results` (type: `string`):

No description

## `output` (type: `string`):

No description

## `files` (type: `string`):

No description

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "watches": [
        "PL4 7",
        "Mutley Plain, Plymouth"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("siteverdict/siteverdict-land-registry-price-alerts").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = { "watches": [
        "PL4 7",
        "Mutley Plain, Plymouth",
    ] }

# Run the Actor and wait for it to finish
run = client.actor("siteverdict/siteverdict-land-registry-price-alerts").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "watches": [
    "PL4 7",
    "Mutley Plain, Plymouth"
  ]
}' |
apify call siteverdict/siteverdict-land-registry-price-alerts --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,siteverdict/siteverdict-land-registry-price-alerts"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/lDHpZ5cVsOejNXnbt/builds/bIIvGajdct0BSAyNu/openapi.json