> For the complete documentation index, see [llms.txt](https://docs.os.uk/os-downloads/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.os.uk/os-downloads/products/land-and-terrain-portfolio/os-mastermap-sites-layer/os-mastermap-sites-layer-technical-specification/enumerations/accessmechanismvalue.md).

# AccessMechanismValue

### AccessPoint feature

Defines the values for the possible mechanism of the access permitted at the access point.

| Value           | Description                                                 |
| --------------- | ----------------------------------------------------------- |
| Appointment     | Access is only available by a pre-arranged appointment.     |
| Official Pass   | Access is only available by production of an official pass. |
| Pay and Display | Access is only available by pay and display mechanism.      |
| Pay on Foot     | Access is only available by pay on foot mechanism.          |
| Payment         | Access is only available by a payment.                      |
| Valid Ticket    | Access is only available by production of a valid ticket.   |

{% hint style="info" %}
All values in the preceding table are not currently populated in OS MasterMap Sites Layer.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.os.uk/os-downloads/products/land-and-terrain-portfolio/os-mastermap-sites-layer/os-mastermap-sites-layer-technical-specification/enumerations/accessmechanismvalue.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.