> 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/system-and-structure/wcp-stub-rollers/overview-and-features.md).

# Overview and Features

Our Stub Roller System provides a highly modular platform for teams to create a variety of rollers. Constructed from high-strength aluminum, this system delivers a lightweight yet robust solution for your robot. The stub design allows for easy roller installation and removal by using the stub wrench and the included mounting bolt. We offer pulley end hubs, SplineXL end hubs, and regular end hubs, enabling you to utilize belts and gears for powered rollers, or configure them as idler rollers as needed.

<figure><img src="https://4135010533-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZFpeyLzrE29cgyWyQDsF%2Fuploads%2FkAnqyrDPUVQQ8PrK9Nr0%2FStub%20Roller%20-%20Group%20Cover.svg?alt=media&amp;token=51818469-93c2-4a18-bfdb-e3ecf14cb36e" alt="" width="563"><figcaption></figcaption></figure>

### Notable Features

* Lock nut built into the end of each shaft
* Flats on shafts allow for easier roller removal
* Internal snapring grooves on hubs
* 1-3/4", 2-1/4", 2-3/4" stub shaft lengths
* Pulley end hubs, SplineXL end hubs, and regular end hubs available


---

# 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/system-and-structure/wcp-stub-rollers/overview-and-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.