> For the complete documentation index, see [llms.txt](https://docs.paragontruss.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.paragontruss.com/training/welcome-to-the-paragon-training-academy.md).
# Welcome to the Paragon Training Academy
The Paragon Training Academy aims to provide a "guided" training experience. Our Core Curriculum courses cover introductory and intermediate skills that can be applied by all users; however, some features included in the courses may only be available for certain plans. [Check your account type](https://services.paragontruss.com/account) if you're not sure which Paragon plan you currently have.
Our team is hard at work organizing content into course formats. You can see currently available and planned courses below.
## Core Curriculum
{% hint style="warning" %}
The documentation and training modules provided by Paragon are for educational and informational purposes only, are general in nature, and are not intended to conform to all TPI and TPIC standards. In the event that any documentation or training modules do not conform with the TPI or TPIC standard, the standard takes precedence and supersedes any documentation or training modules published to docs.paragontruss.com or training.paragontruss.com.
{% 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.paragontruss.com/training/welcome-to-the-paragon-training-academy.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.
