> For the complete documentation index, see [llms.txt](https://docs.inferix.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.inferix.io/verifier-node-guide/what-is-verifier-node/how-to-run-verifier-node.md).
# How to run Verifier Node
### 1. **Meet with the minimum requirements:**
> **Standard Verifier Node**
>
> the minimum requirements for a single license for Standard Verifier Node are as follows:
>
> * 1 $$\texttt{x}$$64 CPU Core 2.1 GHz
> * 8 GB RAM
> * 10 GB disk space
> * 10 Mbit/s internet connection
> **Mobile Verifier Node**
>
> The minimum requirements for a single license for Mobile Verifier Node are as follows:
>
> * Octa-core (2.2 GHz Cortex-A55 or equivalent)
> * 4 GB RAM
> * 10 GB disk space
> * 10 Mbit/s internet connection
>
> ***Remark.*** *Mobile verifier node can be used only for PoR verification tasks. This type of node cannot run other types of verification.*
> **Secure Verifier Node**\
> The minimum requirements for a single license for standard verifier node are as follows:
>
> * 1 xx64 Intel®️SGX Core™️ 2.1 GHz CPU
> * NVIDIA GeForce RTX3090 GPU
> * 8 GB RAM
> * 10 GB disk space
> * 30 Mbit/s internet connection
### Detailed guide on how to run the Inferix Verifier Client will be available soon.
---
# 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.inferix.io/verifier-node-guide/what-is-verifier-node/how-to-run-verifier-node.md?ask=&goal=
```
`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.