> 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/all-roles-common-endpoints/h2m-verifiable-credential-endpoints/openid4vp-endpoints/verifier-metadata-openid4vp.md).

# Verifier Metadata (OpenID4VP)

{% hint style="info" %}
Specifications and best practice implementations for Verifiable Credentials are currently being developed. This page is expected to be updated, closely following these developments.
{% endhint %}

The `GET` request to the `/.well-known/openid-verifier` endpoint provides discovery information about the verifier, including supported presentation request formats, presentation endpoint URL, authorization endpoint URL, and other metadata required for OpenID4VP verifiable presentation flows.

{% hint style="info" %}
The `GET` request to the `/.well-known/openid-verifier` is an **OPTIONAL** endpoint and is part of iSHARE Framework's Verifiable Credentials support in line with **OpenID for Verifiable Presentations (OpenID4VP)**.
{% endhint %}

### Endpoint

```
GET /.well-known/openid-verifier
```

The base URL for this endpoint may be published in the [capabilities endpoint](/all-roles-common-endpoints/capabilities.md) under `publicServices` with identifier `"OpenID4VPVerifierBaseUrl"` for verifier roles.

### Request model

There are no request parameters defined.

### Example request

```
GET /.well-known/openid-verifier
Host: verifier.ishare.eu
```

### Response model

The response is a JSON object containing the Verifier Metadata as specified in [OpenID4VP Section 6](https://openid.net/specs/openid-4-verifiable-presentations-1_0.html#name-verifier-metadata).

* `verifier`\
  **String**. <mark style="color:red;">(Required)</mark>\
  The URL of the Verifier. This MUST be the base URL used to construct verifier endpoints.
* `authorization_endpoint`\
  **String**. <mark style="color:red;">(Required)</mark>\
  The URL of the Authorization Endpoint where presentation requests are initiated.
* `presentation_endpoint`\
  **String**. <mark style="color:red;">(Required)</mark>\
  The URL of the Presentation Endpoint where verifiable presentations are submitted.
* `presentation_definition_supported`\
  **Array of Objects**.\
  Array of supported presentation definition formats.
* `vp_formats_supported`\
  **Object**.\
  Object containing supported verifiable presentation formats (e.g., `vc+sd-jwt`, `mso_mdoc`).

### Example response

```json
{
  "verifier": "https://verifier.ishare.eu",
  "authorization_endpoint": "https://verifier.ishare.eu/authorize",
  "presentation_endpoint": "https://verifier.ishare.eu/presentation",
  "presentation_definition_supported": [
    {
      "format": "vp_token",
      "presentation_definition_uri_supported": true
    }
  ],
  "vp_formats_supported": {
    "vc+sd-jwt": {
      "cryptographic_binding_methods_supported": [
        "did:web"
      ],
      "cryptographic_suites_supported": [
        "ES256"
      ]
    }
  }
}
```


---

# 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://dev.ishare.eu/all-roles-common-endpoints/h2m-verifiable-credential-endpoints/openid4vp-endpoints/verifier-metadata-openid4vp.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.