Questions, answered straight.

Through a phone bridge. You create a worker in the dashboard and open their Pair device QR code. The Android companion app scans it and calls POST /api/v1/auth/pair with the device identifier. The glasses talk to the phone, the phone talks to Cleer — the glasses never call the API directly in the pilot.

No. Scanners keep talking to your WMS exactly as they do today. Cleer doesn't replace them — it adds a hands-free channel and then updates your WMS through a signed webhook. The two stay in sync through Cleer, not by rewiring your scanner fleet.

For the pilot, Cleer needs connectivity. There's no offline buffering or store-and-forward yet — if the phone can't reach the API, the action isn't recorded until connectivity returns. Offline mode is on the post-pilot roadmap.

Worker identity (name, employee code, role), a PIN hash, device identity, command transcripts, and any evidence images captured during a command. Raw audio is not stored. See the Security page for the full pilot-scope picture.

No. The pilot uses Meta glasses in Developer Preview status. That means developer hardware and preview APIs — the glasses layer is intentionally thin, and the warehouse logic lives entirely in Cleer. If Meta's developer terms change, Cleer can move to another wearable without touching the warehouse rules.

Two ways. For reads, create an API key in the dashboard and poll the customer API (/api/customer/v1/…). For writes, give Cleer a webhook URL — it POSTs signed stock-change events that you verify with your webhook secret. Full details are in the interactive API reference.