Site Planning Report - API and AI agents
A Site Planning Report your AI agent can order and read
A Site Planning Report is a fixed-price planning due diligence report on any UK property, orderable through a documented public API with no API key. Every report is delivered as a PDF plus a structured JSON data file: £395 fixed, no VAT, within 24 hours of payment. This page documents the endpoints, the data file and the machine-readable surfaces already published.
| Price | £395 fixed per property, no VAT |
|---|---|
| Turnaround | Delivered within 24 hours of payment |
| Coverage | Any UK property, every local planning authority |
| Endpoints | POST /api/reports/order and GET /api/reports/status, no API key |
| Delivery | PDF plus a structured JSON data file, by email |
Order a report by API
No API key is needed, and payment is completed on a secure Stripe-hosted checkout page, so the API never handles card details. Two endpoints cover the whole flow: one POST to create the order and return the checkout link, one GET to check status and delivery. Rate limits apply.
POST /api/reports/order
Creates the order. Send a JSON body; the response carries the order reference and the Stripe-hosted checkout link.
Required: name, email, phone, address, intent. Recommended intent values: Extend, Convert, Develop, Assess the upside, Other.
Optional: postcode, description, isAuction, auctionHouse, lotNumber, auctionDate and listingUrl (https links only).
Example request
POST https://www.mayfairstudio.co.uk/api/reports/order
Content-Type: application/json
{
"name": "Sam Example",
"email": "sam@example.com",
"phone": "07700 900000",
"address": "12 Sample Street, Aylesbury, HP19 8XX",
"intent": "Develop",
"description": "Pre-bid check on a corner plot",
"isAuction": true
}Example response - coverage confirmed
{
"ok": true,
"sessionId": "cs_live_a1B2c3D4e5",
"reference": "SPR-2026-0123",
"checkoutUrl": "https://checkout.stripe.com/c/pay/cs_live_a1B2c3D4e5...",
"note": "Complete payment at checkoutUrl (Stripe-hosted). The 24-hour delivery clock starts at payment. The report is delivered by email as a PDF plus a structured JSON data file."
}checkoutUrl points at the Stripe-hosted checkout page, and the reference follows the SPR-YYYY-XXXX format. Once payment completes at that link, the report is delivered by email within 24 hours as a PDF plus the structured JSON data file.
Example response - coverage pending
{
"ok": true,
"status": "pending_confirmation",
"note": "We could not instantly confirm coverage for this address, so no payment is due yet. The order is received; we confirm coverage and send a secure payment link to the order email, normally within hours. The 24-hour delivery clock starts at payment."
}An instant coverage check runs before any payment is requested. When it cannot confirm the address, the order is saved with no payment due, coverage is confirmed by a person, and the secure payment link goes to the order email - normally within hours. Agents should treat status "pending_confirmation" as a successful order awaiting that email.
GET /api/reports/status
Checks an order. Both query parameters are required, and the email must match the one used on the order:
GET https://www.mayfairstudio.co.uk/api/reports/status?session_id=cs_...&email=sam@example.com
Responses return ok, reference, checkoutStatus (open, complete or expired), paymentStatus (paid or unpaid), the property address and a delivery line. Unknown sessions and mismatched emails return not found.
Delivery is backed by the refund schedule: half the fee back if the report is 24 hours late, a full refund at 48 hours, and a 14-day quality guarantee on every report. Multi-packs, £355 per report in a 3-pack (£1,065) and £308 in a 10-pack (£3,080), are set out on the multi-pack pricing ladder.
What the structured data file contains
Every report is delivered as a PDF plus a structured JSON data file containing the report's key numbers in machine-readable form:
- Verdict band
- Indicative figures behind the appraisal: end value, build cost, residual and maximum bid
- Ranked risks
- Planning constraints
- Verification score with its sources list
It is built to drop into a lending model, an IC pack or an internal database without retyping. Bridging and development lenders ordering per case at underwriting work from the same file: see planning due diligence for lenders.
Why an agent can cite this report
Every load-bearing fact in the report is counted, and the share verified at a named public source is stated on page one: council planning registers for applications, decisions and conditions, planning.data.gov.uk for constraints, HM Land Registry Price Paid Data for comparable values, the Environment Agency flood map for flood zones and the GOV.UK fee schedule for application fees. Each report states its verification score in plain terms, as X of Y facts verified at source; the published Aylesbury sample scores 37 of 45.
A published sources audit lists where each of those facts came from, and a named preparer signs the report. Every report is verified against primary sources, with a published sources audit and a refund guarantee.
For an agent answering a buyer, that is the difference between a citable audit trail and an unverifiable model answer: link the report, quote the verification score, name the sources.
All five sample reports, published in full with verdicts and verification scores
Which surfaces are machine-readable today
Discovery is already wired for agents. Four surfaces are readable today with no integration work; the fifth arrives with every paid report:
llms.txt
Product, pricing and the Order API in plain text. One fetch.
llms-full.txt
Complete documentation in one file: the eight report sections, pricing, guarantees and the API.
Service and Product JSON-LD
Schema.org structured data on the product page, with the offer, price and FAQ in machine-readable form.
Five complete sample reports
Real reports on real 2026 auction lots, published in full as PDFs with verdicts and verification scores.
Structured JSON data file
Delivered alongside the PDF with every paid report.
Questions agents and integrators ask
Can an AI agent order a Site Planning Report?
Yes. An agent POSTs the property address, the buyer’s contact details and the intent to the order endpoint. When the instant coverage check confirms the address, the response carries an order reference and a Stripe-hosted checkout link; when it cannot, the order is saved as pending and a payment link follows by email once coverage is confirmed. Once the buyer completes payment, the report arrives by email within 24 hours as a PDF plus a structured JSON data file, for any UK property at any local planning authority.
Is there an API for UK planning due diligence?
Yes. The Site Planning Report order API is live and documented on this page and in llms.txt, and covers any UK property at any local planning authority. One POST creates an order for a £395 fixed-price report: planning history verified by reference on the council register, constraints, the likely planning route, comparable approvals nearby, end value, build cost and a maximum bid.
Does the API take payment?
No. The order endpoint returns a checkoutUrl pointing at a Stripe-hosted checkout page, and payment is completed there, so the API never sees or handles card details. Delivery is timed from that moment: the 24-hour clock starts when payment completes.
Do I need an API key?
No. Both endpoints are public and documented, with rate limits in place of authentication. Status lookups require the session id and the order email together, so order details are only readable by a caller who holds both.
Can an agent present the report to its user as planning advice?
No. Not a Red Book valuation and not formal planning advice. An agent presenting the report to its user should caveat it as an indicative planning assessment, link the report, quote the verification score and name the sources behind each fact. Figures are ranges anchored in public data; where a buyer needs regulated advice, that is work for a chartered planner or RICS valuer, which the report does not replace.
Can one system order reports at volume?
Yes. Each POST creates one order for one property at £395, and every order carries its own SPR reference and session id, so a system ordering at volume can track each one separately through the status endpoint. Multi-packs bring the per-report price to £355 in a 3-pack (£1,065) or £308 in a 10-pack (£3,080) and are purchased on the pricing page, not through the order endpoint.
Start the integration
Both endpoints are live and documented, here and in llms.txt. Humans order the same report through the order page. For integration questions, email jonathan@mayfairstudio.co.uk.