> For the complete documentation index, see [llms.txt](https://docs.verifone.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.verifone.com/cug-57.01-en/commander-user-reference-57.01/pos-workstations-overview.md).
# POS Workstations Overview
Verifone Point of Sale (POS) devices typically use the Verifone Commander as the server.
## Verifone C18
Verifone C18 is Verifone’s most powerful, integrated POS for convenience stores with unsurpassed functionality and versatility. Verifone C18’s user interface is made for cashiers serving customers who want a frictionless experience. The brilliant, high definition screen is easy on the eyes. At an impressive 18.5 inches, there is abundant real estate for all sales needs.
Verifone C18
### App Selector
The Verifone C18 POS screen can be positioned to Home (cashier facing) or Flip (customer facing) and can be orientated to render applications in landscape or portrait orientations at Home and Flip positions.
This hardware capability facilitates running multiple cashier and customer facing applications in portrait and landscape orientations.
{% hint style="info" %}
*Refer to the* [*App Selector*](/feature-references/features-and-products-references/app-selector.md) *User Reference documentation for more information on this feature.*
{% endhint %}
***
---
# 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://docs.verifone.com/cug-57.01-en/commander-user-reference-57.01/pos-workstations-overview.md?ask=&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.
