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

# Supported Integrations

> The devices, transports and playback protocols Melody supports today.

This page lists what is available right now. Anything not on it is not supported.

## Melody device

The Melody device is the only hardware you can drive through the Melody API directly.

| Transport            | Entry point                                                           | What it carries                                                                                                                        |
| -------------------- | --------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------- |
| **WiFi — REST**      | `https://api.getmelody.io` → [`/device/*`](/melody/wifi/device_setup) | Device info and status, settings, stroker setup, playback control, firmware and debug                                                  |
| **WiFi — WebSocket** | `wss://api.getmelody.io/api/haptics/ws`                               | [Subscribing](/melody/streaming/subscription) to live haptic frames                                                                    |
| **BLE**              | GATT services `0x1001`–`0x2003`                                       | [Local control](/melody/ble/setup) without a network: WiFi provisioning, device status, OTP, and the HDC / HPS / HLC playback services |

Playback protocols, and where each one runs — the full field reference is in
[Playback Protocols](/melody/wifi/playback_protocols):

| Protocol                        | Transport | Purpose                                                               |
| ------------------------------- | --------- | --------------------------------------------------------------------- |
| **HSC** — Haptic Script Control | WiFi only | Timeline playback of a funscript you upload, orchestrated server-side |
| **HDC** — Haptic Direct Control | WiFi, BLE | Direct stroke commands                                                |
| **HPS** — Haptic Points Stream  | WiFi, BLE | High-frequency point stream, interpolated on the device               |
| **HLC** — Haptic Loop Control   | WiFi, BLE | Looping motion between two positions                                  |

## Other brands, through Haptics Connect Hub

Third-party devices are not reachable through the Melody API. They are served by a separate
service — **Haptics Connect Hub** — which exposes one API over every brand and translates it
to each vendor's own cloud. Access is granted per organization; contact
[support@getmelody.io](mailto:support@getmelody.io).

| Brand         | Transport                             | HDC | HPS | HSC | HLC | Command rate |
| ------------- | ------------------------------------- | --- | --- | --- | --- | ------------ |
| **Melody**    | Melody API (WiFi)                     | ✓   | ✗   | ✓   | ✓   | 200 / s      |
| **Handy**     | Vendor cloud API (v2 and v3 firmware) | ✓   | ✓   | ✓   | ✓   | up to 60 / s |
| **Autoblow**  | Vendor cloud API                      | ✓   | ✗   | ✓   | ✓   | \~2 / s      |
| **VacuGlide** | Vendor cloud API                      | ✗   | ✗   | ✓   | ✓   | \~2 / s      |

Point streaming to a Melody device goes through the Melody API rather than the hub. The rates are
the ceiling each vendor's API allows, not a Melody limit; the hub reports the live per-device matrix
on its capabilities endpoint, and that answer wins over this table.

## Not supported

* Brands outside the four above, including anything reachable only over a vendor's own BLE
  protocol — the hub talks to vendor clouds, not to third-party hardware directly.
* Driving a third-party device through `api.getmelody.io`. Brand support lives in the hub.