Lingzhu now uses a minimal one-step binding flow.
DeepScientist serves the Lingzhu-compatible routes directly on its own daemon / web port:
GET /metis/agent/api/healthPOST /metis/agent/api/sse
For a real device binding, the address registered on Rokid must be the public DeepScientist address that external devices can reach. It cannot be 127.0.0.1, localhost, or a private-network address.
References:
- Rokid developer forum: https://forum.rokid.com/post/detail/2831
- Rokid agent platform: https://agent-develop.rokid.com/space
Make sure:
- DeepScientist is already running
- the DeepScientist page you opened is the final public address that external devices should use
- if the current page is local-only or private-network-only, Lingzhu should not be saved yet
Settings > Connectors > Lingzhu now keeps only the necessary pieces:
- one
Add Lingzhu (Rokid Glasses)entry point - the Rokid platform screenshot
- the auto-generated copyable fields
- concise binding instructions
- one save action
You no longer need to manually edit host, port, agent, OpenClaw snippets, or extra probe steps in the main flow.
After you click Add Lingzhu (Rokid Glasses), the popup shows these copyable values:
- Custom agent ID
- Custom agent URL
- Custom agent AK
- Agent name
- Category
- Capability summary
- Opening message
- Input type
- Icon PNG URL
Important details:
Custom agent URLis generated ashttps://<your-public-address>/metis/agent/api/sseAKis generated automatically and reused after saving- the logo uses a PNG DeepScientist asset so it can be uploaded directly to Rokid
On the Rokid platform:
- Open
Project Development -> Third-party Agent -> Create - Choose
Custom Agent - Copy each generated field from the popup into the matching Rokid field
- Upload the DeepScientist PNG logo
- Return to DeepScientist and click Save
After Save, the Lingzhu binding is complete.
The glasses or platform only need to call:
POST /metis/agent/api/sse
with:
Authorization: Bearer <saved-AK>
Usage rules:
- a new task must start with
我现在的任务是 ... - only the text after that prefix is treated as a fresh DeepScientist task
- if you only want buffered progress, do not repeat the prefix; just say
找DeepScientistor继续
Because Rokid and external devices cannot reach your local loopback address. Lingzhu must register a public address.
Because AK is the Bearer secret for this external entrypoint. Generating and persisting it is safer and more reliable than asking users to type it manually.
No. The goal of the current Lingzhu flow is to show only the necessary values, let the user copy them, and finish with one save.

