> 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/polycord-pulleys/overview-and-features.md).
# Overview and Features
Do you need a single pulley? A double? A triple? You can have 1,323 pulleys, or even more, all by stacking a single part! Our new stackable pulleys allow you to have as many (or as little) pulleys as you’d like by stacking a single part over and over and over. The stackable pulleys are designed to fit together seamlessly, and are sized such that the outer diameter of a 1/4” polycord cable on the pulley is either 1.625” or 2” to match with our flex wheel sizes.
## Notable Features
* Same width as our original polycord pulleys in the same configuration
* Infinitely stackable
* Sized so that the polycord touches the object, not the pulley
* Designed with piloting pins and pockets to make assembly a breeze
---
# 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/polycord-pulleys/overview-and-features.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.
