> For the complete documentation index, see [llms.txt](https://docs.dextoros.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dextoros.app/get-started/connect-your-first-robot.md).

# Connect your first robot

Generate a connector, run one install command and pair a real robot.

{% hint style="warning" %}
**Draft.** Some details on this page are still being confirmed and may change. Questions? Email <info@dextoros.app>.
{% endhint %}

Connecting a robot takes one command. Each robot gets its own connector with its endpoint and pairing key filled in.

{% stepper %}
{% step %}

## Name the robot

Enter a **Robot name** of up to 32 characters, for example `AMR-11`.

DextorOS turns the name into a slug for files and endpoints: lowercase letters and numbers, with everything else replaced by `-`. `AMR-11` becomes `amr-11`.
{% endstep %}

{% step %}

## Choose the platform and transport

Pick the **Platform** that matches the robot's body:

* 6-axis arm
* Warehouse AMR
* Quadruped
* Mobile manipulator
* Humanoid
* Delta picker

Then pick the **Transport** the robot speaks: WebSocket, MQTT, ROS 2, Serial or Test mode. See [Transports](/connect-robots/transports.md) for what each one writes into the connector.
{% endstep %}

{% step %}

## Download the connector file

Download `dextoros-connector.yaml`. It holds the robot's name, platform, transport settings and pairing key:

```yaml
# DextorOS connector for amr-11
robot: amr-11
platform: warehouse-amr
transport: websocket
endpoint: wss://fleet.dextoros.app/robots/amr-11
pairing_key: <filled in for you>
report:
  - capabilities
  - telemetry
  - events
```

{% endstep %}

{% step %}

## Install on the robot

Run this once on the robot's onboard computer, replacing `amr-11` with your robot's slug:

```bash
curl -fsSL https://fleet.dextoros.app/install/amr-11.sh | sh
```

{% endstep %}

{% step %}

## Wait for the first connection

The robot moves through three states:

1. **Waiting for first connection**
2. **Handshake** with your robot
3. **Live**

On first connection the robot reports its capabilities, such as wheeled base, LiDAR and depth camera. From then on it streams telemetry up to DextorOS and receives commands back.
{% endstep %}
{% endstepper %}

```mermaid
sequenceDiagram
    participant R as Robot (connector)
    participant D as DextorOS
    R->>D: First connection with pairing key
    D-->>R: Handshake
    R->>D: Capabilities
    loop While live
        R->>D: Telemetry and events
        D-->>R: Commands
    end
```

{% hint style="warning" %}
Changing the robot's name, platform or transport after pairing means you need to reinstall the connector to reconnect.
{% endhint %}

## Next steps

* [Keys and pairing](/connect-robots/keys-and-pairing.md)
* [Console commands](/fleet-and-console/console-commands.md)


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.dextoros.app/get-started/connect-your-first-robot.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
