> 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/greyt/greyt-elevator-cascade/overview-and-features/general-specs.md).
# General Specs
## Base Height
The heights shown in the image below are for the elevator represented in the CAD model. The only limits on the height of the elevator are the lengths of the tubing sold, which is 47".
## Maximum Extension Height
The heights shown below are for the existing elevator presented in the CAD models. Modifying the lengths of the tubes will result in your elevator having a different max height.
All dimensions are in inches.
## Elevator Width Limitations
The carriage width has a lower limit of 8" wide, but there is no maximum width. That limit is determined by the user. The widths of all other stages are determined by the carriage. See the page on [Material Cutting](/welcome/greyt/greyt-elevator-cascade/assembly-instructions/material-cutting.md) for more information.
---
# 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/greyt/greyt-elevator-cascade/overview-and-features/general-specs.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.
