> 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/bearing-blocks/overview-and-features.md).

# Overview and Features

The WCP Bearing Blocks provide a simple and easy solution to mounting bearings to a tube. Perfect for the "West Coast" style drivetrain, these bearing blocks provide multiple ways to accomplish the same goal: adding a slot to the tube for the more customizable Sliding Bearing Blocks, or simply clamping around the tube with the easier Clamping Bearing Blocks.

<figure><img src="https://860767938-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FAh7kNj2G3b1j9BJvKAXk%2Fuploads%2Frm5C7GszfhFWOd1JJbHd%2FBearing%20Block%20-%20Cover.svg?alt=media&amp;token=50753fd1-808e-49a2-bcf7-4abd955a879c" alt=""><figcaption></figcaption></figure>

## Clamping Bearing Blocks Features

* 2" and 2.5" width, allowing for multiple simple gear trains
* Clamps around 1" and 2" tall box tubes
* Can trap the flange of the bearing against the tube with the c-bore
* All #10-32 hardware
* Come with and without the 0.0625" center drop
* Compatible with all parts with the MotionX pattern
* SplineXL ID allows for torque transfer through the center of the block
* Compatible with the WCP Cam

## Sliding Bearing Blocks Features

* Compatible with the WCP Cam
* 2" center distance for tapped holes


---

# 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/bearing-blocks/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.
