Developer

LimbBot API

Developer SDK and integration toolkit with ROS 2 node, REST controls, telemetry, and deployment utilities.

Overview

LimbBot API

Gives software teams stable interfaces to integrate LimbBot into robot stacks and cloud workflows.

  • ROS 2 node and SDK bindings
  • REST endpoints for jobs and registry actions
  • Telemetry schemas for runtime and guard events
  • Deployment packaging and examples
Key features

What it does

Capabilities are scoped for robotics teams building pilots and production fleets.

ROS 2 node and SDK bindings

LimbBot API supports this capability as part of the developer layer for whole-body control programs.

REST endpoints for jobs and registry actions

LimbBot API supports this capability as part of the developer layer for whole-body control programs.

Telemetry schemas for runtime and guard events

LimbBot API supports this capability as part of the developer layer for whole-body control programs.

Deployment packaging and examples

LimbBot API supports this capability as part of the developer layer for whole-body control programs.

How it works

LimbBot API workflow

Connect

Provide robot model, interfaces, and deployment constraints.

Configure

Set product-specific parameters, permissions, and success metrics.

Validate

Run simulation, lab, or telemetry checks before promotion.

Operate

Use logs and reviews to improve the next policy or release.

Specs

Technical profile

AreaDetailsNotes
Primary roleDeveloperDeveloper SDK and integration toolkit with ROS 2 node, REST controls, telemetry, and deployment utilities.
Runtime pathEdge or cloud depending on productreal-time control stays on robot for Core
InterfacesROS 2, SDK, REST, telemetryvaries by program
NVIDIA stackIsaac, Jetson, CUDA/TensorRT, OpenUSDused where relevant
Gallery

Abstract product view

Visual placeholder showing how this product fits in the LimbBot control platform.

  • Control plane and data path are separated
  • Robot runtime receives approved versions
  • Telemetry returns for review
  • Safety gates control promotion
Use cases

Where LimbBot API is used

Use cases depend on program maturity and robot body class.

Quadruped inspection

Validate walking and recovery over industrial routes.

Industrial humanoids

Support balance during payload and tool tasks.

Research platforms

Benchmark morphologies and control approaches.

OEM scale

Package reusable control into shipped robot programs.

Pricing teaser

Licensed with the LimbBot platform

Pricing depends on body class, product mix, fleet size, and cloud usage. Most teams start with a pilot scope.

  • Pilot fee for integration and validation
  • Per-robot runtime licensing where applicable
  • Cloud fine-tuning or simulation usage
  • OEM royalty structures for scale
Questions

LimbBot API FAQ

LimbBot API is for robotics teams that need the developer capability described on this page.

It can be evaluated alone, but production programs often combine multiple LimbBot products.

Robot model, compute target, interfaces, and a bounded first task.

Policies and configurations move through validation and safety review before robot rollout.

Related products

Build the rest of the stack

Most deployments combine runtime, safety, simulation, cloud adaptation, planning, and API integration.

Runtime

LimbBot Core

On-robot whole-body control runtime for balance, locomotion, and payload-aware motion at the edge.

View product
Cloud

LimbBot Studio

Cloud fine-tuning and dynamics adaptation for new bodies, payloads, terrains, and tasks.

View product
Simulation

LimbBot Sim

GPU simulation and reinforcement-learning pipeline built on NVIDIA Isaac for contact-rich robot motion.

View product
Safety

LimbBot Guard

Safety layer for fall avoidance, force limits, stop modes, and event telemetry around learned control.

View product
Planning

LimbBot Planner

Agentic loco-manipulation motion planner that composes sub-skills for long-horizon mobile manipulation.

View product

Add LimbBot API to your robot program

Share your robot class and first task to scope integration.

Request access