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

# Help Center

<h2 align="center">Welcome to Synteq documentation</h2>

<p align="center">Browse the categories below or use the buttons on the right top to contact us!</p>

<p align="center"></p>

<table data-view="cards"><thead><tr><th></th><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><h4><i class="fa-money-bill-wave">:money-bill-wave:</i></h4></td><td><strong>Client Portal</strong></td><td>Self-service help, account management, and billing</td><td><a href="https://legacy.docs.synteq.com/client-portal/">Client Portal</a></td></tr><tr><td><h4><i class="fa-hard-drive">:hard-drive:</i></h4></td><td><strong>Dedicated Servers</strong></td><td>Server management and configuration</td><td><a href="https://legacy.docs.synteq.com/dedicated-servers/">Dedicated servers</a></td></tr><tr><td><h4><i class="fa-server">:server:</i></h4></td><td><strong>Virtualization Platform</strong></td><td>VPS control, configuration, and panel guides</td><td><a href="https://legacy.docs.synteq.com/virtualization-platform/">Virtualization Platform</a></td></tr><tr><td><h4><i class="fa-microchip">:microchip:</i></h4></td><td><strong>GPU VDS</strong></td><td>Installation guides and environment setup</td><td><a href="https://legacy.docs.synteq.com/gpu-vds/">GPU VDS</a></td></tr><tr><td><h4><i class="fa-network-wired">:network-wired:</i></h4></td><td><strong>Networking</strong></td><td>Network configuration and troubleshooting</td><td><a href="https://legacy.docs.synteq.com/networking/">Networking</a></td></tr><tr><td><h4><i class="fa-terminal">:terminal:</i></h4></td><td><strong>System Administration</strong></td><td>Server management and maintenance</td><td><a href="https://legacy.docs.synteq.com/system-administration/">System Administration</a></td></tr></tbody></table>

<h3 align="center"><strong>Frequently asked questions</strong></h3>

<details>

<summary>Do you accept cryptocurrencies?</summary>

Yes, we do. BTC is natively supported, and other coins are supported through [trocador.app](https://trocador.app).

</details>

<details>

<summary>Do you offer free trials?</summary>

No, we do not, though we do have a 3-day no questions asked refund policy! ([ToS applies](https://synteqhpc.com/legal/tos))

</details>

<details>

<summary>Where can I find your looking glass?</summary>

You can find it here: <https://synteqhpc.com/looking-glass>.

</details>

<details>

<summary>Do you have a status page?</summary>

Yes, we do, and it's available here: [https://status.synteqhpc.com](https://status.synteqhpc.com/).

</details>

<details>

<summary>How can I contact you?</summary>

You can contact us using the buttons on the right top of the screen.

</details>

<details>

<summary>Do you offer discounts for bulk purchases?</summary>

Yes, we do in some cases. Please reach out to us with your request using the buttons on the right top of the screen.

</details>


---

# 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://legacy.docs.synteq.com/readme.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.