> For the complete documentation index, see [llms.txt](https://help.opslinkservers.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.opslinkservers.com/getting-started/browsing-servers.md).

# Browsing Servers

In this page you will find a tutorial on browsing servers and features including commenting, reporting, etc.

{% hint style="warning" %}
Submitting False Reports or Inappropiate Comments will result in moderation against your account!
{% endhint %}

***

> Too browse servers that are approved and listed on OpsLink Servers simply head too the website <https://www.opslinkservers.com/> and click the "Browse Servers" Button!&#x20;

***

### Reviews & Reporting

> Too place a review on a server you must be logged in on the website and from there you will go to the "Browse Servers" Page and find the server you would like to leave a review on, then you will click it too bring up it's server profile and leave a review there!

***

> Too report a server do the same actions you did too leave a review except click the red report button next too the join button and leave your report there!

<a href="https://www.opslinkservers.com/servers/" class="button primary" data-icon="link">Browse Servers</a>


---

# 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 following URL with the `ask` and `goal` query parameters:

```
GET https://help.opslinkservers.com/getting-started/browsing-servers.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 `build a script that syncs our docs to a CMS` 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.