ISACAI / VLAClaw

Skill-Orchestrated Embodied AI for ROS2 Robots

VLAClaw connects OpenClaw intelligence with ROS2-enabled robots through rosbridge, enabling voice interaction, visual perception, validated skill execution, and closed-loop embodied control.

OpenClaw plans at the validated skill layer while ROS2 controllers handle real-time robot execution.
Open API Portal
OpenClaw RuntimeROS2 / rosbridgeRaspberry Pi 5 GatewayVLM / LLM Skill Planning
9090rosbridge WebSocket endpoint
SkillAI output boundary
ROS2stable execution layer
Closed loopsensor-to-skill feedback
1Voice / Text / Camera
2OpenClaw Agent Runtime
3Skill Planner + Server
4rosbridge WebSocket
5ROS2 Robot Controller
6Robot Dog / Arm / Display
Platform Surface

A product portal backed by developer infrastructure.

ISACAI brings the company website, API portal, skill schema, rosbridge integration patterns, demo workflows, and bilingual product documentation into one connected platform surface.

Internal API Portal

A companion API website for internal development, robot-agent integration, skill interfaces, and team-side documentation.

http://isacai.space

Open isacai.space

Company product website

Public narrative layer

Explains ISACAI, VLAClaw, product positioning, safety philosophy, roadmap, team, and cooperation paths.

Developer API website

Internal platform layer

Supports internal developers with API-oriented documentation and a clearer path from robot capability to agent integration.

Skill schema and examples

Execution contract

Defines how action groups, motion commands, sensor reads, and interaction behaviors become validated robot skills.

rosbridge integration design

Robot connectivity layer

Documents WebSocket JSON patterns for ROS2 topic subscription, command publishing, and future service calls.

Demo workflow library

Deployment workflow

Frames voice greeting, visual interaction, safe patrol, and developer integration as repeatable demo workflows.

Bilingual product materials

Product communication layer

Makes the platform understandable to labs, robot teams, education customers, OEM partners, and Hong Kong / mainland collaborators.

Integration Packages

Focused deployment programs for robot teams and partners.

ISACAI provides structured integration programs that connect ROS2 robots, skill libraries, OpenClaw workflows, and developer APIs into working embodied AI experiences.

ROS2 Robot Integration Sprint

For labs or robot teams with an existing ROS2 robot.

Interface audit
rosbridge setup
first 5 skills
sensor subscription demo
integration report
A robot can be controlled through the VLAClaw skill layer instead of a manual-only upper computer.

Education Demo Kit

For universities and AI/robotics courses.

Skill library template
developer API examples
lecture-ready architecture diagrams
voice command demo plan
student project topics
A course or workshop can teach ROS2, OpenClaw, VLA, and skill orchestration with one coherent story.

Exhibition Interaction Prototype

For showrooms, innovation showcases, and interactive product demonstrations.

Voice greeting script
action-group skills
display expression flow
operator safety panel
demo runbook
A reliable staged interaction with clear operator controls, repeatable workflows, and visible safety boundaries.
FAQ

Platform questions, answered.

Key answers about VLAClaw, ROS2 integration, Skill Server boundaries, developer access, and deployment workflows.

Is VLAClaw a robot controller?

VLAClaw is an intelligent upper-computer and skill orchestration layer. Robot-side ROS2 nodes remain responsible for real-time motion and hardware control.

Does the AI directly output motor commands?

The model outputs skill choices and bounded parameters. Skill Server validates the command before ROS2 executes the underlying action.

Do developers need to install ROS2 on the host?

Not for the primary integration path. The host can connect through rosbridge WebSocket and JSON messages while the robot runs ROS2.

What can be evaluated first?

Teams can review the architecture, Skill API, rosbridge examples, action-group mapping, developer workflows, and demo runbooks, then connect the same contracts to robot-side ROS2 systems.

Which robots are easiest to support?

ROS2-enabled quadruped robots are the first target. Any robot with stable command interfaces, sensor topics, and emergency stop behavior is a candidate for integration.