> For the complete documentation index, see [llms.txt](https://docs.pandium.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pandium.com/connectors/connectors-101/coach-packet.md).
# Coach Packet
Set up the Coach Packet connector in Pandium using your secret key so tenants can securely sync college coach recruiting and athlete evaluation event data.
## **Connector Overview**
Coach Packet by NCSA has everything college coaches need to find and evaluate athletes at large events.
## **Authentication Type**
Basic
## **Webhook Supported**
No
## **Secrets**
PAN\_SEC\_COACHPACKET\_SECRET\_KEY
## **API Client Supported**
No
## **Requirements for Provisioning**
No provisioning is required for this connector.
## **API Resources**
For more information on how to utilize the Coach Packet API, please contact Coach Packet support directly.
---
# 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.pandium.com/connectors/connectors-101/coach-packet.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.
