# Account Manager Talks to Unitree's cloud API directly — no phone app required. Sign in with your Unitree credentials (or paste an access token), and the same surface area the mobile app uses opens up: device list, firmware images, tutorials, sharing, raw API console.

## Sign-in Two paths: - **Email + password** — standard login, session is persisted in `localStorage` and refreshed automatically. - **Access token** — paste an existing `accessToken`; useful if you've fetched one with the `unitree-fetch-aes-key` CLI from [unitree_webrtc_connect](https://github.com/legion1581/unitree_webrtc_connect) or extracted it from the phone app. The **family slot** on the landing page determines which `AppName` header signs cloud requests — `Go2` accounts hit `global-robot-api.unitree.com` with `AppName: Go2`; G1 accounts use `AppName: B2`. Pick the one your account is registered under. ## Tabs ### Devices Robots bound to your account: online status, alias, SN, model, firmware version. Per-device actions: bind/unbind, share, fetch firmware images, view detail. Logging in here also primes the AES-128 key cache for any V3-capable device (G1 ≥ 1.5.1, Go2 ≥ 1.1.15) by pulling `dev.key` from `device/bind/list`. The device detail screen also exposes a **Refresh AES Key** panel (between Firmware Updates and Danger Zone). Paste the 344-char base64 blob from the BT page (`344B RSA` row) and the cloud will RSA-decrypt it via `device/bindExtData`, persist the derived 16-byte key as `dev.key`, and seed the local cache — useful when a device was bound before its firmware moved to V3, or after a key rotation. Family-agnostic: the call's `AppName` header is pinned to the device's series, so refreshing a G1 key while logged in as Go2 family (or vice versa) works. ### Info App version with APK download links, grouped video tutorials (queried as `tutorial/list?appName=&type=`), changelog, and announcements. ### Account Profile, avatar, password change, region, session management. ### Debug Raw API console — 77 endpoints across 13 categories (Auth, Devices, Firmware, WebRTC, Wallet, etc.). Lets you fire any cloud request with custom params and inspect the JSON response. Useful for protocol reverse-engineering or one-off operations that don't have a dedicated UI yet.