> 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.1/participant-registry-role/getting-started.md).

# Getting started

The Data Space Governance Body admits members to the data space. The Participant Registry serves as the Trust Anchor for the data space, a crucial aspect in any iSHARE use case. Each participant in the data space can verify in the Participant Registry whether other parties in the data space are trusted and compliant. These are prerequisites, however, which is why it does not play a direct role (and is not depicted) in any of the use cases.

To register all participants in the data space and ensure that the coverage by the Framework is digitally verifiable, the Participant Registry is built on a Distributed Ledger across all data spaces, using the iSHARE Trust Framework as the core component. This means all data spaces operating based on the Trust Framework are interoperable by design.\
\
With the Participant Registry, data space governance body/administrators can register participants. For participant administration, a web interface (Participant Registry) or APIs for automated registration are available. Automated participant discovery in data spaces is facilitated through defined endpoints that offer key insights for data spaces to operate:

*Parties End-point*\
Retrieve data from a selection of parties available in the data space or in a subset of the data space. It will look like this (example where the iSHARE DID method is used as identifier): /parties/did:ishare:EU.NL.NTRLNL-10000000.

Every node implementation is equipped with API’s and with that can serve within the data space as the single source for party information with the performance level of the data space.

In order to double check if required endpoints are implemented, please use the following list as a cheat sheet:

Participant Registry

* [ ] [Access Token (M2M)](https://dev.ishare.eu/version-2.1.1/all-roles-common-endpoints/access-token-m2m.md)
* [ ] [Capabilities](https://dev.ishare.eu/version-2.1.1/all-roles-common-endpoints/capabilities.md)
* [ ] [Parties](https://dev.ishare.eu/version-2.1.1/participant-registry-role/parties.md)
* [ ] [Trusted list](https://dev.ishare.eu/version-2.1.1/participant-registry-role/trusted-list.md)
* [ ] [Versions](https://dev.ishare.eu/version-2.1.1/participant-registry-role/versions.md)
* [ ] [Data Spaces](https://dev.ishare.eu/version-2.1.1/participant-registry-role/dataspaces.md)
* [ ] [Create Entitled Party](https://dev.ishare.eu/version-2.1.1/participant-registry-role/create-entitled-party.md)


---

# 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.1/participant-registry-role/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.
