> For the complete documentation index, see [llms.txt](https://help.verkada.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.verkada.com/command-connector/es/readme.md).

# Command Connector

Añade cámaras no Verkada a tu organización de Command de forma rápida, fácil y fiable

**Resumen**\
Command Connector te permite integrar cámaras que no son de Verkada en la plataforma basada en la nube Verkada Command, ofreciéndote una interfaz de gestión unificada. Proporciona una forma rentable de migrar a la videoseguridad basada en la nube mientras se preservan las inversiones actuales en hardware.

Esta colección te guía sobre cómo agregar un Command Connector, conectar cámaras compatibles que no son de Verkada (ONVIF-Profile S) y traerlas a Command para su visualización y gestión centralizadas. Command Connector admite funciones principales de la plataforma como monitoreo de video en vivo, retención de video y análisis básicos como búsqueda de personas y vehículos.

Consulta estos enlaces para empezar:

<table data-view="cards"><thead><tr><th></th><th data-type="content-ref"></th></tr></thead><tbody><tr><td></td><td><a href="/command-connector/es/primeros-pasos/get-started-with-command-connector.md">Empieza con Command Connector</a></td></tr><tr><td></td><td><a href="/command-connector/es/primeros-pasos/command-connector-network-settings.md">Configuración de red de Command Connector</a></td></tr><tr><td></td><td><a href="/command-connector/es/instalacion/prepare-for-a-command-connector-deployment.md">Prepárate para una implementación de Command Connector</a></td></tr></tbody></table>


---

# 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://help.verkada.com/command-connector/es/readme.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.
