# What data schema does Rabbit R1 expect for pairing with OpenClaw

**URL:** <https://forum.rabbitcommunity.tech/t/what-data-schema-does-rabbit-r1-expect-for-pairing-with-openclaw/15751>\
**Category:** general chat\
**Created:** [April 5, 2026, 7:57am UTC](https://forum.rabbitcommunity.tech/t/what-data-schema-does-rabbit-r1-expect-for-pairing-with-openclaw/15751 "2026-04-05T07:57:30Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![PaulBacon](https://avatars.discourse-cdn.com/v4/letter/p/58f4c7/32.png) [@PaulBacon](https://forum.rabbitcommunity.tech/u/PaulBacon)\
**Post date:** [April 5, 2026, 6:19pm UTC](https://forum.rabbitcommunity.tech/t/what-data-schema-does-rabbit-r1-expect-for-pairing-with-openclaw/15751/3 "2026-04-05T18:19:11Z")

</div>

Have a look at this post: [how to connect your r1 to OpenClaw (formerly Moltbot/Clawdbot) - #9 by simon](https://forum.rabbitcommunity.tech/t/how-to-connect-your-r1-to-openclaw-formerly-moltbot-clawdbot/15646/9)

If you see “Invalid QR Format” on VPS/public setups, the key point is:

- local network setups can use insecure WS,
- but remote/VPS setups need a valid SSL domain + WSS on port 443.

So don’t use raw public IP + ws QR for internet-facing pairing. Use a tunnel/proxy setup (e.g. Cloudflare Tunnel), point it to localhost:\<openclaw\_port\>, then generate QR with the public hostname and port 443, scan, and approve pairing.

Also keep token auth enabled and avoid exposing OpenClaw directly without TLS/proxy protection.

---

_[View the full topic](https://forum.rabbitcommunity.tech/t/what-data-schema-does-rabbit-r1-expect-for-pairing-with-openclaw/15751)._