Partners & prototypes

Confidant One protocol

In development

Software interface for a future wearable. Test with the Companion simulator today. Physical manufacturing is separate and not for sale here.

Honest constraints

  • No camera in the v1 concept
  • No on-device AI — Confidant OS answers; device speaks the reply
  • Never auto-calls emergency services
  • No fictional specs, launch dates, or order buttons

Pairing

  1. User generates a short-lived code in Companion → One
  2. Device POSTs /api/os/one/claim with code + deviceKey
  3. OS returns a deviceToken once — store securely
  4. Later calls use Authorization: Bearer <deviceToken>

Optional factory header when OS_HARDWARE_PAIRING_SECRET is set: x-confidant-device-secret

API surface

  • POST /api/os/one/claim(claim)
  • POST /api/os/one/heartbeat(heartbeat)
  • POST /api/os/one/voice(voice)
  • POST /api/os/one/button(button)

Button actions

  • assist — Quick help from Confidant OS
  • guardian_start — Begin a check-in session
  • guardian_ok — Confirm during Guardian
  • guardian_end — End the session
  • circle_alert — Notify trusted people — not 911

Full notes for prototype partners live in the repo as docs/CONFIDANT_ONE_HARDWARE.md. This page is not a bill of materials for mass production.

Try simulatorDevelopers

Partner / prototype interest

Interest only — not an order. No payment is taken, and no shipping date is promised. Physical hardware is not for sale here.

Partner / manufacturing interest (not an order)

Confidant One protocol | Confidant