What problem does it solve? Building live, per-second biometric data streams from wearables requires navigating a producer/broker/consumer architecture, an opcode-framed websocket handshake, single-use tokens, and platform-specific SDK setup, where small protocol mistakes cause silent failures or reconnect loops. ## Core Features & Use Cases - Websocket protocol guidance: Covers the wss://ws.tryterra.co/connect handshake, IDENTIFY roles, heartbeats, close codes, and REPLAY backfill with exclusive bounds. - Token architecture: Explains the three single-use token types (phone-registration, producer, consumer) and how to mint them server-side per session. - Per-platform RT SDK setup: Reference guides for iOS, Android, React Native, Flutter, and Wear OS producers, including Apple Watch workout sessions and ANT+ support. - Use Case: A backend engineer needs to consume live heart-rate data from users' BLE chest straps; the skill walks through minting a consumer token, completing the IDENTIFY handshake, handling sparse seq gaps, and backfilling missed data with REPLAY after a drop. ## Quick Start Ask the agent to help you build a backend consumer that connects to the Terra streaming websocket and receives live heart-rate data from a test user.
