> For the complete documentation index, see [llms.txt](https://learn.trenchacademy.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://learn.trenchacademy.xyz/perps/introduction.md). # Introduction This section is built for anyone taking their first steps into perpetual trading.

		Cover image	Cover image (dark)
Core Mechanics of Perps	Understands how perp trading works	Core Mechanics of Perps.png	Core Mechanics of Perps-1.png	Core Mechanics of Perps
Risk Management	Learn to protect your capital	Risk Management.png	Risk Management-1.png	Risk Management
Common Beginner Mistakes	Avoid errors made by new traders	Common Beginner Mistakes.png	Common Beginner Mistakes-1.png	Common Beginner Mistakes
Simple Pre-Trade Checklist	Confirm the essentials before entering	Simple Pre-Trade Checklist.png	Simple Pre-Trade Checklist-1.png	Simple Pre-Trade Checklist

*** If you already know the basics and want to learn more, checkout [Framework](/perps/framework.md) --- # 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://learn.trenchacademy.xyz/perps/introduction.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.