> 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/getting-started/tutorial/deploying-verifier.md).

# Deploying the Verifier

**What We Are Doing:**

* Creating a Verifier service using One-Click Deployment.

**Why:** The Verifier ensures that presented credentials are valid, coming from a trusted Issuer, and meet the required criteria. It automates cryptographic checks and provides a simple API.

**Steps:**

1. In the One-Click Deployment platform, create a new Verifier.
2. Once active, note down necessary details. These variables can be found after clicking on the Verifier Details in the One-Click Deployment portal.
   * `VERIFIER_SERVICE_URL` (e.g., `https://your-verifier.evdi.app`) (the URL where the Verifier is hosted)
   * `VERIFIER_CLIENT_SECRET` (e.g., `your-verifier-secret`) (the secret used to authenticate requests to the Verifier)
3. Store these in your `.env` file so your application can access them securely:

   ```
   VERIFIER_SERVICE_URL=https://your-verifier.evdi.app
   VERIFIER_CLIENT_SECRET=your-verifier-secret
   ```

After storing these details in .env, they will be easily accessible in your code using `process.env.VERIFIER_SERVICE_URL` and `process.env.VERIFIER_CLIENT_SECRET`, and you can use them in your CMD or terminal to interact with the Issuer service (to use it you muse run `source .env` in your terminal).

Next, we will configure a verification flow in our backend.


---

# 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/getting-started/tutorial/deploying-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.