Property summary
property_summaryOne call that says what a property is, which building it belongs to and its headline attributes; the place to start when the question is about a specific address.
Same call over REST
Property summary/v1/property/{uprn}/summaryNot connected yet? Connect your assistant. Sign in with your MarketCode account; no API key needed.
Reference
What property_summary answers
When someone asks about a specific property, this usually answers the question on its own: what it is (type, tenure where known), the building it belongs to and how many units that building holds, and the headline attributes drawn from the sources the platform joins at the UPRN. It costs 4 credits because the response carries licensed AddressBase and building records, and it is the cheapest way to get an oriented view before deciding which of the deeper tools to call.
Reference
When to use it, and when not to
Use it first for any question about one address, after resolving the UPRN. If the answer needs depth, go on to the specialist tools: valuation_full for the value and its evidence, transactions_by_uprn and property_history for the sales, epc_certificates for the energy history, council_tax_band for the band, ownership_by_title for the proprietor. property_lookup returns the full record in tiers with a source and a confidence beside every field, up to about three hundred of them, and is the right call when you want everything rather than the summary.
Inputs
Before you call it
A UPRN. address_autocomplete (free) narrows the address; address_resolve (8 credits) returns the UPRN. Once you have it, this and every other per-property tool takes it directly.
- uprn
- A UPRN is the Unique Property Reference Number every UK address carries. Narrow the address with address_autocomplete, which is free, then address_resolve returns the UPRN for 8 credits. property_summary and address_by_postcode return UPRNs too.
Example
An example call to property_summary
Use the MarketCode tool property_summary with {"uprn":"200003443835"} and show me the result.{
"uprn": "<string>",
"country": "<string>",
"data": {
"data": {
"subject": {
"uprn": 0,
"parent_uprn": 0,
"address": "<string>",
"postcode": "<string>",
"classification_code": "<string>"
},
"summary": {
"parent_uprn": 0,
"building_name": null,
"n_comps": 0,
"gbp_per_sqm_median": null,
"gbp_per_sqm_iqr_low": null,
"gbp_per_sqm_iqr_high": null,
"gbp_per_sqm_min": null,
"gbp_per_sqm_max": null,
"gbp_per_sqft_median": null,
"year_built": null,
"year_built_period": "<string>",
"num_floors": 0,
"construction_material": "<string>",
"roof_shape": "<string>",
"basement_presence": "<string>",
"building_footprint_m2": 0
}
}
},
"credits_charged": 0
}Shape only. This call returns licensed records, so the keys are real and every value is a placeholder of its type.
Inputs
Arguments property_summary takes
| Name | Type | Required | Description |
|---|---|---|---|
| uprn | string | Yes |
Response
What comes back
| Field | Type |
|---|---|
| uprn | string |
| country | string |
| data | object |
| data.data | object |
| data.data.subject | object |
| data.data.subject.uprn | integer |
| data.data.subject.parent_uprn | integer |
| data.data.subject.address | string |
| data.data.subject.postcode | string |
| data.data.subject.classification_code | string |
| data.data.summary | object |
| data.data.summary.parent_uprn | integer |
| data.data.summary.building_name | null |
| data.data.summary.n_comps | integer |
| data.data.summary.gbp_per_sqm_median | null |
| data.data.summary.gbp_per_sqm_iqr_low | null |
| data.data.summary.gbp_per_sqm_iqr_high | null |
| data.data.summary.gbp_per_sqm_min | null |
| data.data.summary.gbp_per_sqm_max | null |
| data.data.summary.gbp_per_sqft_median | null |
| data.data.summary.year_built | null |
| data.data.summary.year_built_period | string |
| data.data.summary.num_floors | integer |
| data.data.summary.construction_material | string |
| data.data.summary.roof_shape | string |
| data.data.summary.basement_presence | string |
| data.data.summary.building_footprint_m2 | number |
| credits_charged | integer |
Fields observed in the example response above; a field the example did not exercise is not listed.
Reference
Things that catch people out
- The building matters as much as the unit. Flats share a building, and comparables, physical form and some auction records are matched at building level. The summary names the building so later calls can be read in that light.
- Null is unknown, not absent. Where a source has no value for a field the field is omitted or null; the response does not estimate it. The full record's provenance says which fields came from where.
- Coverage differs by source. The address is Great Britain; sales, ownership and council tax are England and Wales; planning designations are England. A Scottish property summarises with gaps, and says so.
Usage
How to run property_summary in your assistant
Ask your assistant in plain English, for example:
"Use the MarketCode tool property_summary for <address or area>.
Show the result and the credits charged."
The arguments the assistant will send, for the example on this page:
{"uprn":"200003443835"}The connect steps for Claude, ChatGPT, Codex, Cursor and Claude Code are on the MCP page.
Skills
Skills that use property_summary
- Property research: A sourced answer to any UK property question: the right tool for the job, the credit cost stated first, the wording rules that keep an estimate an estimate.
- Valuation report: An indicative valuation for one address: the range, the comparables and adjustments, the index position, the EPC, flood and planning context, and the reasoning, with every figure cited to the tool it came from.
- Deal analysis: A first-pass appraisal of a site or asset: plot utilisation, planning position, market evidence, value and a residual against the cost assumptions you supply.
- Planning check: Every designation and constraint at an address, recent applications nearby and the flood position, laid out the way a planner reads them.
Price and licence
What it costs, and where the data comes from
property_summary costs 4 credits per successful call over MCP and over REST, and the two surfaces share one credit balance.
The price covers licensed records in the response, from Ordnance Survey, Valuation Office Agency and Ministry of Housing, Communities and Local Government. A call that fails is not charged.
Credits are granted on sign-up and bought in packs; the pricing page lists every call.
Sources
- Ordnance Survey
AddressBase
Used under licence from Ordnance Survey · Great Britain
- Valuation Office Agency
Council tax valuation list
Crown copyright · England and Wales
- Ministry of Housing, Communities and Local Government
Energy Performance Certificates (domestic and non-domestic)
MHCLG's EPC open data terms · England and Wales
Related
Tools used with property_summary
- Full property record5 credits
property_lookupFull property record for a UPRN, grouped into tiers: identity, property,Pairs with this - Resolve an address to a UPRN8 credits
address_resolveResolve free-text address to canonical record (UPRN for UK).Pairs with this - Full valuation with back-seriesFree
valuation_fullFull valuation block for a property: the value and its range, a monthlyPairs with this - EPC certificates for a propertyFree
epc_certificatesEvery Energy Performance Certificate lodged against a property, newest first, with current and potential efficiency, CO2, heating fuel and system, floor area and construction age.Pairs with this - Registered sales for a propertyFree
transactions_by_uprnAll HMLR Price Paid records joined to this UPRN, newest first.Pairs with this - Comparable properties6 credits
property_compsComparable properties in the same building or block, with missingSame product
Glossary
Terms used here
- UPRN: The Unique Property Reference Number: a 12-digit identifier every addressable location in Great Britain carries, and the key MarketCode joins property records on.
- Council tax band: The A to H (A to I in Wales) valuation band the Valuation Office Agency assigns every domestic property, based on its value at 1 April 1991 (2003 in Wales); read from the list, never predicted.
- Model Context Protocol (MCP): An open protocol that lets an AI assistant discover and call tools on a remote server; MarketCode exposes every data operation as an MCP tool that Claude, ChatGPT, Codex and Cursor can call.
- Read-only tool: A tool annotated on the server as never changing anything, so an assistant can call it without a confirmation step; every MarketCode tool is read-only.
FAQ
Questions about property_summary
How much does `property_summary` cost?
+
property_summary costs 4 credits per successful call over MCP and over REST, and the two surfaces share one credit balance. The price covers licensed records in the response, from Ordnance Survey, Valuation Office Agency and Ministry of Housing, Communities and Local Government. A call that fails is not charged.
Do I need to resolve the address first?
+
Yes. property_summary takes a UPRN, not an address. Start with address_autocomplete (free) to narrow the address, then address_resolve (8 credits) to get the UPRN. An assistant with the MarketCode skills installed does both steps on its own.
Which assistants can run `property_summary`?
+
Any MCP client: Claude (claude.ai, Claude Desktop, Claude Code), ChatGPT in developer mode, Codex and Cursor, each documented on the MCP page. You sign in with your MarketCode account over OAuth; there is no key to paste, and the connection is read-only.
Where does the data come from?
+
Read from Ordnance Survey AddressBase, Valuation Office Agency council tax list and Ministry of Housing, Communities and Local Government EPC register. Coverage is Great Britain for the address; England and Wales for most attributes.
Can I store or republish the results?
+
The response includes records we license from Ordnance Survey, Valuation Office Agency and Ministry of Housing, Communities and Local Government. Use them in your own analysis, reports and products; bulk redistribution of the raw records or building a competing dataset from them is not covered. Ask us if you need a redistribution licence.
Does `property_summary` change anything?
+
No. The tool is annotated read-only on the server, so it never writes to your data or ours and an assistant can call it without a confirmation step.
Summary or full record?
+
Summary when you want to orient in one call and pay 4 credits; full record (property_lookup, 5 credits) when you want every field with its source and confidence, grouped into identity, property, energy, building, land, risk, designations, infrastructure, ownership and provenance.
Does it include the value?
+
The headline attributes are the record, not the model. Call valuation_estimate (free) for the number or valuation_full for the number with its evidence; an assistant running the valuation skill does both after the summary.
Why does it cost credits when the valuation is free?
+
Because the response includes licensed records (AddressBase for the address and Ordnance Survey building data), and licensed data is priced per call. The valuation is MarketCode's own model over public sales and certificate data, so it is free.
Try property_summary in your assistant.
30-minute call. We'll connect your assistant live on a real address.