> 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/electronics/kraken-x60/kraken-x60-motor/overview-and-features/cooling-port.md).
# Cooling Port
To help with cooling, the Kraken X60 has (2x) #10-32 tapped holes on the side. This allows teams to install up to (2x) pneumatic fittings to assist with cooling motors between matches or while practicing at home for extended periods of time.
Having two cooling ports gives teams the option of plumbing motors together, allowing for a single inlet to push air through multiple motors at once.
An example of two different ways teams can use the cooling ports on the motors.
{% hint style="danger" %}
The cooling ports provide a pathway into the motor and should be protected when not in use. An unprotected cooling port can allow debris to enter the motor and can cause **permanent damage** to the motor.
{% endhint %}
{% hint style="danger" %}
**Is cooling required?**
No. This is an optional feature that was added for teams practicing at home. Forcing cool air into the motors can reduce the downtime between practice matches. All thermal testing was done without actively cooling the motors.
{% endhint %}
---
# 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/electronics/kraken-x60/kraken-x60-motor/overview-and-features/cooling-port.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.
