> For the complete documentation index, see [llms.txt](https://docs.cybus.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cybus.io/2-1-1/documentation/industry-protocol-details.md).
# Industry Protocol Details
Configure protocols and connectors to connect your industrial devices.
This chapter documents the protocols and connectors supported by Connectware and provides detailed configuration parameters for each. These protocols and connectors enable connections between Connectware and various industrial devices and systems in your environment.
The following sections provide detailed specifications for each supported protocol, including connection parameters, data formats, security considerations, and configuration examples. These specifications will help you implement reliable connections to your existing industrial equipment.
Connectware's protocol support is regularly updated. For protocols not listed in this documentation, you can create [Custom Connectors](/2-1-1/documentation/industry-protocol-details/custom-connectors.md) or [contact us](https://www.cybus.io/en/resources/support-center/) to discuss alternative connectivity options.
## Discover Industry Protocols and Connectors
---
# 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.cybus.io/2-1-1/documentation/industry-protocol-details.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.
