# Why a Data Request API

Given the rough state of exercising data rights, many solutions could be put forward. Why propose an API for data requests? The argument we make is that a standardised Data Rights API offers more technically robust, secure, accessible and compliant data rights experience. All the while, organisations have the opportunity to reduce compliance costs by following best practices, rather than inventing them.

{% content-ref url="/pages/-MN86QKSazdDHblP1OVH" %}
[Security](/why-a-data-request-api/security.md)
{% endcontent-ref %}

{% content-ref url="/pages/-MN86QKR9J3i7hsv9l1N" %}
[Modularisation](/why-a-data-request-api/modularisation.md)
{% endcontent-ref %}

{% content-ref url="/pages/-MN8OBXaMqM6ZxGo178w" %}
[Best practices](/why-a-data-request-api/best-practices.md)
{% endcontent-ref %}

{% content-ref url="/pages/-MN8OFGr4FZw\_Au7QNxo" %}
[A great user experience](/why-a-data-request-api/a-great-user-experience.md)
{% endcontent-ref %}


---

# Agent Instructions: 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:

```
GET https://whitepaper.open-data-rights.org/why-a-data-request-api.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.