> 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/gearboxes/wcp-swerve-x/overview-and-features/key-features.md).

# Key Features

* All configurations of the module use the same shafts. What this means is users can swap between every configuration and mounting style by simply using different plates.&#x20;
* Less hardware required for assembly.&#x20;
* Easy to install encoder locations
* Modules accept multiple motors: Kraken X60 - 775pro - 550 motors.&#x20;
* The bottom mounting plates are made of 7075-T6 to help with bending.&#x20;
* Wheel height is the same regardless of configuration, so it is possible to mix and match modules on the robot.&#x20;
* New optional aluminum bevel gear is available to shave off weight.&#x20;
* Alignment holes to zero module.&#x20;
* Clearance holes so motors can be removed without disassembling gearbox.&#x20;
* Smaller and lighter 3” ID X-contact bearing.
* Gears Below configuration give much greater protection to the drive and rotation first stage gears and motor shafts.


---

# 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/gearboxes/wcp-swerve-x/overview-and-features/key-features.md?ask=<question>&goal=<user_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.
