> For the complete documentation index, see [llms.txt](https://docs.parloa.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.parloa.com/welcome-to-parloa.md). # Welcome to Parloa Your starting point for product knowledge, learning, and updates across the platform.


AMP Documentation	Step-by-step guides to build and manage agents in Parloa.	AMP Documentation
Additional Documentation	The documentation spaces below require you to login separately. You must be whitelisted. Please contact your Parloa representative.	RBA Documentation	RTT Documentation
Academy	Available for partners and customers. Please contact your Parloa representative.	Academy
Release Notes	See AMP's new features, enhancements, and important product updates.	Release Notes
Developer	This is a collection of developer guides covering how to set up, configure, and integrate an AI agent platform with your own systems and channels.	Developer Documentation

--- # 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://docs.parloa.com/welcome-to-parloa.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.