> For the complete documentation index, see [llms.txt](https://support.senterasensors.com/home/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.senterasensors.com/home/6x-series-sensors-user-guide/integration-information/communication-protocol/custom-integration.md).

# Custom Integration

Software tools and examples for integrating 6X cameras into custom applications.

Use this page to find software examples for integrating a 6X camera into your own application or platform. For hardware interfaces and communication details, see the related documentation below.

## Sentera Camera Tools

[**Explore the Sentera Camera Tools repository on GitHub →**](https://github.com/SenteraLLC/sentera-camera-tools)

Scripts and examples for customers and integrators building Sentera camera support into their projects. The repository includes:

* Test APIs demonstrating camera communication and common workflows.
* A 6X example for connecting to the camera's ROS bridge.
* Setup and usage guidance to help you get started.

Refer to the repository's README for setup requirements and instructions for each example.


---

# 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://support.senterasensors.com/home/6x-series-sensors-user-guide/integration-information/communication-protocol/custom-integration.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.