DavidBuchanan314

The Rabbit R1 uses a few custom APIs to talk to The Cloud™. Almost nothing happens on-device, and all the AI magic happens on servers.

Consequently, you don't really need the physical device.

TLS Client Fingerprinting

In lieu of an authentication scheme, Rabbit's servers attempt to verify device authenticity by checking the TLS client's JA3 fingerprint, presumably enforced by AWS WAF.

If your TLS client doesn't match an expected fingerprint, you'll get HTTP 403 errors. This fingerprint works:

DavidBuchanan314

The R1 checks for updates by querying https://ota.transactional.pub/qa/{Build.DISPLAY}.json, where {Build.DISPLAY} is the current build.

The JSON file returns metadata for a delta update package.

Known values of Build.DISPLAY:

• rabbit_OS_v0.8.50_20240407162326

• rabbit_OS_v0.8.67_20240420094131