> ## Documentation Index
> Fetch the complete documentation index at: https://docs.checkthatfield.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Attribution

> What you must show wherever you show our data, and how to treat planning applications.

Our scores are built from public data, much of it under Crown copyright or the Open Government Licence. Those licences ask for credit wherever the data is shown. So does Check That Field.

## What to show

Wherever you show data from the API, show:

1. **Every line of the answer's `attribution` array**, word for word, near the data.
2. **A credit to Check That Field**, with a link to [checkthatfield.com](https://www.checkthatfield.com).
3. **A short note** that the scores are an automated indicator from published data, not planning or legal advice.

"Near the data" means on the same page or screen, where a reader can find it without leaving: under a map or table, or in a footer or info panel beside it.

> [!TIP]
>
> Take the lines from each answer rather than copying them into your code. If a licence changes, the answer changes with it.

## The `attribution` array

Every answer from `/v1/scores` and `/v1/fields/{field_id}` has an `attribution` array of strings. Today it holds these lines:

> [accordion] Field boundaries (HM Land Registry INSPIRE)
>
> This information is subject to Crown copyright and database rights \[year] and is reproduced with the permission of HM Land Registry. The polygons (including the associated geometry, namely x, y co-ordinates) are subject to Crown copyright and database rights \[year] Ordnance Survey AC0000851063.

> [accordion] Ordnance Survey and Royal Mail
>
> Contains OS data © Crown copyright and database right. Contains Royal Mail data © Royal Mail copyright and database right.

> [accordion] Open Government Licence
>
> Contains Environment Agency, Natural England and Office for National Statistics data, licensed under the Open Government Licence v3.0.

> [accordion] Planning applications
>
> Planning applications: the councils' public planning registers; each links to the council's page, which is the official record.

The first line is the statement HM Land Registry asks for with its INSPIRE index polygons, which give each field its outline. Show it whenever you show our fields, outlined or not: the scores are worked out field by field from those outlines.

The planning applications line comes only when the answer includes applications. If you call `/v1/scores` with `applications=false`, it is left out, and you needn't show it.

> [!NOTE]
>
> Show the lines as given. Don't shorten, merge or reword them.

## Planning applications

The applications in our answers come from the councils' public planning registers. We pass on the register's facts only: the reference, address, proposal, type, homes proposed, status, decision, dates and where we placed it.

* **The council's page is the official record.** Each application's `url` links to it. Link to it wherever you show an application, so readers can check the details and see the documents there.
* **No documents, no names.** We don't pass on plans, letters or other documents, or the names of applicants, agents or anyone who commented. Don't add them from elsewhere beside our data.
* **Say how it was placed.** `located_by` says how we put an application on the map: `published` (the council's own location), `postcode` (the postcode in its address) or `address` (the words of its address). Positions placed by postcode or address are approximate.

## The widget does this for you

The [widget](https://docs.checkthatfield.com/widget/overview.md) shows the attribution and a link to the full report itself. You don't need to add anything around it.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.