> For the complete documentation index, see [llms.txt](https://dev.ishare.eu/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://dev.ishare.eu/version-2.1/entitled-party/getting-started.md).

# Getting started

The Entitled Party's role is fulfilled by a legal entity that has appropriate entitlement over a set of data. The entitlement provides the party with one or more rights over the data. These rights, or entitlements, are established in a legal relationship between the Entitled Party and the Service Provider when they are different entities. Data may be stored and provided access to as a service to perform various actions over it.

The Entitled Party, Service Consumer and Service Provider roles can be fulfilled by the same entity i.e. a legal entity that consumes a service based on its own entitlements to this service (for example, a trucking company's entitlement to request Estimated Time of Arrival and optimal route information) but this is not necessary.

Entities entitled to a service can delegate others to consume it on their behalf. In such cases, the consuming entity operates based on another entity’s entitlements. In these cases, the Service Consumer uses a Service Provider’s service based on the Entitled Party’s entitlements, but the role of Service Consumer is performed by a different entity than the Entitled Party.


---

# 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://dev.ishare.eu/version-2.1/entitled-party/getting-started.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.
