> 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-3.0/introduction/getting-started/verifiable-credentials.md).

# Verifiable Credentials

This section introduces how Verifiable Credentials (VCs) are used in the iSHARE documentation set and where to find the normative requirements and implementation details. VCs are used to issue, present, and verify signed claims (e.g., membership, roles, mandates) in a portable way, so different parties can validate the same evidence consistently.

In order to implement VC flows, start with the normative specifications, schemas, and then follow the endpoint requirements for your role.

**Next steps:**

* [**VC Specifications**](https://dev.ishare.eu/reference/verifiable-credentials-specifications) (W3C VC / DCP / OpenID4VCI/VP)
* [**Credential schemas**](/version-3.0/reference/credential-schemas.md)
* [**H2M Verifiable Credential endpoints**](/version-3.0/all-roles-common-endpoints/h2m-verifiable-credential-endpoints.md) including [**OpenID4VCI endpoints**](/version-3.0/identity-provider/h2m-verifiable-credential-endpoints/openid4vci-endpoints.md) and [**OpenID4VP endpoints**](/version-3.0/entitled-party/h2m-verifiable-credential-endpoints/openid4vp-endpoints.md), and/or [**M2M Verifiable Credential endpoints**](/version-3.0/all-roles-common-endpoints/m2m-verifiable-credential-endpoints.md) including DCP endpoints (as applicable per role)


---

# 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-3.0/introduction/getting-started/verifiable-credentials.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.