> For the complete documentation index, see [llms.txt](https://docs.creativeconners.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.creativeconners.com/docs/stagehand/stagehand-pro-ac/stagehand-pro-4-unpacking.md).

# Stagehand Pro 4: Unpacking

### What’s In The Box?

{% tabs %}
{% tab title="5 HP" %}

* A welcome card with a quick link to this documentation (cci.fyi/pro4)
* Stagehand Pro 4
* 10ft power cord
* \#10-32 screws (x8) for rack mounting
* Printed electrical schematic
* Mitsubishi A800 instructions on CD
  {% endtab %}

{% tab title="10 HP" %}

* A welcome card with a quick link to this documentation (cci.fyi/pro4)
* Stagehand Pro 4 motion controller
* 10ft power cord
* \#10-32 rackmount screws (x8)
* 2 rear rack ears with 10-32 Button Head Cap Screws
* Mitsubishi A800 instructions on CD
  {% endtab %}
  {% endtabs %}

If any of these items are missing, please [contact us](/docs/technical-support.md) for a replacement. While you’re at it, give us a little sass for forgetting to put something in the box. We enjoy an appropriate amount of sass.

If you purchased any power cables, encoders, limits switches, machines, or other accessories, those items are packaged separately.


---

# 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.creativeconners.com/docs/stagehand/stagehand-pro-ac/stagehand-pro-4-unpacking.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.