> For the complete documentation index, see [llms.txt](https://docs.wcproducts.com/welcome/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.wcproducts.com/welcome/product-info/manuals/gearboxes.md). # Gearboxes

Product	Useful Sections	Cover image
PlanetaryX	Kit Contents Getting Started	PX - Card View.svg	PlanetaryX
Swerve X2	Kit Contents Getting Started	Swerve X2 - Standard - Card View.svg	WCP Swerve X2
Swerve X2S	Kit Contents Advanced Features	Swerve X2S (Throughbore) - Card View.svg	WCP Swerve X2S
1 Motor Gearbox	Kit Contents Getting Started	1 Motor Gearbox, Combined - Card View.svg	1 Motor Gearboxes
Rotation SS Gearbox	Kit Contents Getting Started	Rotation SS - Card View.svg	Rotation SS Gearbox
WCP Single Stage Gearbox	Kit Contents Getting Started	Single Stage - Main.svg	WCP Single Stage Gearbox
WCP SS Flipped Gearbox (Single Speed, 2 Stages)	Kit Contents Getting Started	SS Flipped Gearbox - Card View.svg	WCP SS Flipped Gearbox (Single Speed, 2 Stages)
Swerve X	Kit Contents Getting Started	Card View - Gears Below.svg	WCP Swerve X
Swerve XS	Kit Contents Getting Started	Swerve XS - Card View.svg	WCP Swerve XS
Friction Brake	Kit Contents Getting Started	Friction Brake - Card View.svg	Friction Brake

--- # 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.wcproducts.com/welcome/product-info/manuals/gearboxes.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.