> ## Documentation Index
> Fetch the complete documentation index at: https://doc.kovio.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Quickstart

> Install the Kovio SDK on a Unitree robot in about a minute.

You need three things: a **Unitree G1 / Go2** with its standard Jetson Orin
onboard computer, **internet access** on the robot, and your **Kovio fleet key**
(`kov_live_…`, issued by Kovio).

<Warning>
  Your fleet key is a secret. Don't share it or commit it anywhere. It can be
  revoked at any time.
</Warning>

## Install

<Steps>
  <Step title="SSH into the robot">
    ```bash theme={null}
    ssh unitree@<robot-ip>
    ```
  </Step>

  <Step title="Confirm the robot has internet">
    ```bash theme={null}
    curl https://kovio-api.fly.dev/healthz
    ```

    You should get a small JSON `{"status":"ok",...}` response. The robot's
    internal `192.168.123.x` bus is not internet — make sure its Wi‑Fi / 4G‑5G
    uplink is connected.
  </Step>

  <Step title="Run the installer with your fleet key">
    ```bash theme={null}
    curl -fsSL https://dist.kovio.dev/install.sh | sudo bash -s -- <YOUR_FLEET_KEY>
    ```

    This activates your key, installs the SDK, and starts it as a service that
    runs on every boot.
  </Step>

  <Step title="Watch it come online">
    ```bash theme={null}
    journalctl -u kovio -f
    ```

    Within seconds the robot **registers on your Kovio dashboard**, and within
    about a minute its first verified moments appear. See
    [Instant dashboard updates](/instant-dashboard).
  </Step>
</Steps>

## That's it

No source code is placed on the robot, and there are no build steps — the
installer fetches a signed, prebuilt artifact matched to your robot's runtime.

<Tip>
  Default mode is `sim` (synthetic traffic) so you can confirm the whole path
  works immediately. Switch to live camera/LiDAR with [hardware mode](/modes).
</Tip>

## If something goes wrong

A bad or revoked key, no internet, or an unsupported runtime will **install
nothing** and print a clear message. See [Troubleshooting](/troubleshooting).
