> 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/assembly-instructions/wheel-tread-cutting.md).
# Wheel Tread Cutting
When cutting tread for the Swerve X Wheel, you must know which version wheel you are using. This is indicated on the wheel itself, by the presence of a fifth untapped hole where the ends of the cut tread will meet. The hole in question is indicated in the images below.
{% hint style="info" %}
When bolting the tread to the Swerve X Wheel, use eight 1/2"L #10-32 Bolts for assembly.
{% endhint %}
Updated Wheel
If you are cutting tread for a wheel with the indicated hole, you can use the Updated Tread Pattern shown below. Otherwise, you must use the Old Tread Pattern.
{% tabs %}
{% tab title="Updated Tread Pattern" %}
{% endtab %}
{% tab title="Old Tread Pattern" %}
{% endtab %}
{% endtabs %}
{% hint style="warning" %}
3 Ply Black Neoprene tread was used to determine the overall length and hole spacing for the tread pattern. If using a different tread type, the spacing may be different due to the construction of the tread.
{% 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.wcproducts.com/welcome/gearboxes/wcp-swerve-x/assembly-instructions/wheel-tread-cutting.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.
