> 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/battery-mount-vertical/overview-and-features.md).

# Overview and Features

The Battery Box kit is one of the easiest ways to securely mount your robot battery to your chassis. The box can be mounted via any of its attachment holes or even sandwiched around a piece of 2”x1” tubing. Alongside the battery mount are special features designed to mount the 120 amp main breaker and the battery cable connector, giving teams a strongly-attached, predetermined space for these commonly forgotten control system components. Loose battery parts are a thing of the past with the WCP Battery Box!

<figure><img src="https://1379630225-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPjuCknLElB0fSLHDc41L%2Fuploads%2Fq0eGvvfMoFlIhkuf9Lgj%2FBattery%20Mount%20-%20Cover.svg?alt=media&amp;token=cf726dc3-31c3-4b7c-8721-d0d9b02b7904" alt="" width="563"><figcaption></figcaption></figure>

### Notable Features

• Built in SB50 mount with security hole for connecting SB50 \
• Multiple mounting locations for Main Breaker Mount \
• Mounting holes work with any set of holes with 2” center to center spacing \
• Slots for battery strap&#x20;


---

# 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/battery-mount-vertical/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.