> For the complete documentation index, see [llms.txt](https://help.urbanpiper.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.urbanpiper.com/readme.md). # The UrbanPiper Ecosystem Here you will find all the necessary resources to familiarise yourself with the necessary tools that will come in handy while managing your restaurant's online and offline operations. Take your time to go through the articles, or feel free to jump right to a topic. To make it easy for you to discover the specific topic that you're looking for, you can use the **search** (**`cmd+k`** on your Mac, or **`ctrl+k`** on windows) functionality. ### Jump right in

		Cover image
Getting Started	The common terms	getting-started.png	Basics
Atlas — management console	For managing your back-of-house operations	business-manager-atlas.png	Business Manager
Store Manager (Prime)	For managing your front-of-house operations	store-manager-prime.png	Store Manager
POS Integrations	Enable your POS to work seamlessly	pos-integrations.png	POS Integrations
Ordering Channels	Manage your Ordering channels directly through UrbanPiper, synced seamlessly to your POS.	ordering-channels.png	Ordering Channels
Data & Reports	Comprehensive guides and tutorials on how to access, understand, and utilize data and reports effectively.	data-and-reports.png	Data & Reports

--- # 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.urbanpiper.com/readme.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 `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.