Skip to content

Use with AI

Use with AI

Robot APIs ​

Two interaction patterns serve different application needs: send individual operations, or supply an ongoing joint path.

ROBOT APIs

Your application. Your control path.

Send a complete operation or supply the next part of a motion. Choose how your application works with the robot.

Concept illustration: HORST1000 G2 with request and response tiles
Concept illustration
01 · CONTROL API

Request an operation

Runtime handles planning and execution. Your application follows the result.

Status & I/OPlanningCommands
Explore the Control API
02 · REAL-TIME STREAMING

Supply a motion path

Your controller supplies buffered joint targets and follows the path progress.

External controllerBuffered targets
Streaming preview

Two paths. One robot platform.

Architecture preview
ApplicationControl APIRobot RuntimeExternalControllerRT clientBuffered pathRTModuleRobotAdmission · execution ownerBuffered joint targets

Admission and execution ownership are coordinated by the deployment before combining Runtime commands and direct streaming.

From admission to completion

Integration preview
Application / RT clientRobot RuntimeRT ModuleCoordinate admissionExecution owner assignedSetAxisValues · path_id · buffered samplesPath progressEND · WaitForPathPath completed

The admission arrows describe the integration workflow. Streaming uses the buffered RT client protocol; a dedicated admission adapter is part of the system integration.

EXPLORE THE CONCEPTInteractive teaching model
ApplicationRuntimePreviewMotionMotionPlan / error
Prepared

PreviewMotion returns a MotionPlan without execution. A preview is a separate operation.

This browser model sends no robot commands. Execution ownership and admission must be coordinated before using a direct RT client.

Start with request-based operations ​

Choose Python for gRPC or Node.js for the binary Protobuf WebSocket gateway. The Control API page includes HTTP request and response schemas.

Begin with a status read. Planning-only preview and execution are separate operations; a preview does not move the robot. Use the Runtime connection configuration supplied for your system.