> For the complete documentation index, see [llms.txt](https://developer.openactive.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.openactive.io/guide-to-openactive-on-github/validators.md).

# Validators

Code for validators and the models that drive them.

Validators are used to ensure that published data conforms to OpenActive standards. Note the overall structure of the codebase: a lightweight validator framework that parses the data fed to it and validates it against whatever model files are provided to it.

* [**data-model-validator**](https://github.com/openactive/data-model-validator)**:** The core OpenActive data model validator library.
* [**data-models**](https://github.com/openactive/data-models)**:** The models used by the validator to check conformity. Currently restricted to [Opportunity](https://www.openactive.io/modelling-opportunity-data/) models.
* [**rpde-validator**](https://github.com/openactive/rpde-validator)**:** RPDE validator library
* [**data-model-validator-site**](https://github.com/openactive/data-model-validator-site)**:** Simple web front-end into which the validator may be embedded to provide a simple-to-use UI.
* [**validator-embed-mvp**](https://github.com/openactive/validator-embed-mvp)**:** First pass at the data-model-validator site.
* [**validator-test-json**](https://github.com/openactive/validator-test-json)**:** JSON files for use in testing the validator.


---

# 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://developer.openactive.io/guide-to-openactive-on-github/validators.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.