> For the complete documentation index, see [llms.txt](https://docs.empe.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.empe.io/develop/intro/create_verifier.md).

# Creating a Verifier

A Verifier is created inside your deployment's **operator console** — not as a separate portal deployment. It runs on the same service (and uses the same Keycloak login) as the Issuer; you register a Verifier by binding it to a DID.

1. In the operator console sidebar, open **Verifiers**.
2. In **Available DIDs**, select the DID the Verifier will use to sign authorization requests. If no DID is available yet, open **DIDs** first and create one (a `did:key` or `did:web`).
3. Click **Create Verifier**.
4. Your Verifier appears in the **Verifiers** list, identified by its DID. Open its **Dashboard** to view the Verifier's details (its Verifier ID).

Authorization (presentation) requests are created — and verification sessions tracked — through the Verifier API, not the console: `POST /verifiers/{verifierId}/authorization-requests` (with `/qr-code`) and `GET /verification-sessions/{id}`. The Verifier shares requests as QR codes or deep links, verifies presented **SD-JWT VC** and **JWT-VC-JSON** credentials, and uses the same admin **Bearer token** as the rest of the deployment — see the [Verifier API](/develop/verifier.md) and [Authenticating to Your Deployment](/develop/intro/authenticating-to-your-deployment.md).

You can also create a Verifier programmatically with `POST /agent/verifier` — see the [Verifier API](/develop/verifier.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 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://docs.empe.io/develop/intro/create_verifier.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.