> For the complete documentation index, see [llms.txt](https://whitepaper.open-data-rights.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://whitepaper.open-data-rights.org/future-considerations/certification.md).

# Certification

As the Open Data Rights API find more widespread adoption, ensuring quality of implementation should be a high priority. In order to get more involved in this process, a certification process could be drawn up.

Given that proper governance and regulation has taken place, a certification process could be drawn up for organisations participating in the API. This certification process should include strict and continuous review of API implementations, and the process as a whole. If organisations comply with these standards, they should receive certification. This certification might be operationalized in the form of a check-mark which carries the weight of the Open Data Rights community.

Through such cooperation with organisations, the Open Data Rights API can more closely coordinate and improve the status quo of data requests.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://whitepaper.open-data-rights.org/future-considerations/certification.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
