Build movement intelligence into your tools.

Connect applications, robots and AI agents through Arisole developer interfaces. Create sessions, ingest telemetry and run evaluations with authenticated access.

Connect your data.

Create Motion Sessions, attach video, sensor or telemetry sources, and ingest observations through authenticated REST routes.

Run evaluations.

Compare reference and candidate robot sessions with MotionBench evaluations. Read metrics, events and series as evidence.

Automate your workflow.

Use MCP tools and service accounts with the same scopes and audit trail as REST. Human approval stays required before release decisions.

Explore the APIs.

OpenAPI and the Runtime API & MCP console document live routes. Agent-to-agent interoperability is available as a research preview where supported.

Integration sketch

Create a Motion Session, attach telemetry, ingest observations, then POST a MotionBench evaluation with reference and candidate session IDs. ROS2 bags convert through the offline ros-bridge first.

LeRobot Reliability Suite

Install arisole-eval and compare LeRobot checkpoints locally without an API key. Start at /developers/lerobot for install commands, a measured CloseFridge example, and optional cloud upload.

Public Motion Intelligence routes

Method	Path	Purpose
POST	/v1/motion/sessions	Create a Motion Session
POST	/v1/motion/sessions/:sessionId/sources	Attach a source
POST	/v1/motion/sessions/:sessionId/sources/:sourceId/data	Ingest JSON or CSV observations
GET	/v1/motion/sessions/:sessionId	Read session, sources, metrics and events
GET	/v1/motion/sessions/:sessionId/observations	List observations
POST	/v1/motionbench/evaluations	Compare two robot runs
GET	/v1/motionbench/evaluations/:id	Read an evaluation
GET	/v1/analyses	List human movement analyses
GET	/v1/analyses/:id	Read one analysis
GET	/v1/workspace	Workspace info for the API key

FAQ

How do AI agents request robot evaluations?

Use authenticated Motion API and MCP tools with MotionBench scopes. Service accounts share the same audit log as REST. A2A interoperability remains a research preview.

How do I authenticate to Motion API?

Requests require an x-api-key header with motion:read or motion:write scopes. Keys are issued through guided onboarding.

Where should robotics teams start?

For LeRobot checkpoint compares, start at /developers/lerobot (local arisole-eval, no API key). For cloud Motion Sessions and MotionBench evaluations, see /robot-ci-cd.

Book a Demo Sign In Platform Resources

Loading Arisole. If the interactive app does not start, continue with the public links above.