Give motion
a clear interface.
Understand commands, coordinate frames, state feedback, and the boundaries between a browser and a robot controller.
THE DEVELOPER’S MOTION PLAYGROUND
Robot arms. AI agents. Virtual claws.
Explore the APIs behind the next move—with practical guides and a hands-on browser playground.
Start in simulation. Understand every command.
Ready at home · no hardware connected
01 / Find your direction
From physical-arm architecture to virtual-game interactions. Choose the world you’re building for.
Understand commands, coordinate frames, state feedback, and the boundaries between a browser and a robot controller.
Connect perception, planning, and bounded agent tools. Separate a proposed action from permission to execute it.
Design virtual aiming, drops, and repeatable game state. Explore a practice cabinet with no purchases or real prizes.
02 / A small API. A clear starting point.
Try an actual, local JavaScript state API—not a pretend cloud endpoint. Choose a pose, change the illustrated gripper, and inspect the resulting state.
Three named poses and a small documented interface.
No sign-in, API key, network command, or connected arm.
// Runs locally. No server or hardware.
const arm = ArmAPIDemo.create();
arm.moveTo('reach');
arm.grip(true);
console.log(arm.getState());
// { mode: 'local-demo', pose: 'reach', ... }const arm = ArmAPIDemo.create();
// Receives the initial state, then updates.
const unsubscribe = arm.subscribe(state => {
console.log(state.pose, state.revision);
});
arm.moveTo('lift');
unsubscribe();const arm = ArmAPIDemo.create();
arm.moveTo('reach');
arm.grip(true);
// Restore home + open; keep revision growing.
const state = arm.reset();
console.log(state.pose); // 'home'
console.log(state.gripper); // 'open'03 / Build in the right order
Our guides use a simple design discipline: describe, check, observe, and recover. A drawing is not a physical safety system.
Name the goal, units, coordinate frame, and limits before you ask for motion.
Validate the proposed operation and keep permissions separate from planning.
Distinguish an accepted request from a measured outcome or a local visual change.
Design timeouts, cancellations, and resets before adding a more complicated workflow.
Keep exploring
Start with the contract, not the motor. A practical guide to commands, feedback, capabilities, and a simulation-first workflow.
Give an agent useful skills without unrestricted actuator access. Design narrow tools, reviewable plans, and honest outcomes.
Model aim, descend, close, and return as explicit states. Keep virtual mechanics understandable and independent of frame rate.
04 / Before you start
Know exactly what runs here—and what needs a separate system.
About ArmAPI.comA developer resource for robot arm API design, remote-control architecture, AI workflows, and virtual claw games. The site includes guides, a local JavaScript state library, and two browser demonstrations.
No. Its controls update an illustration in your browser. Physical motion requires a separate controller integration, verified hardware behavior, and application-specific safeguarding. Start with the safety and scope notes.
No hosted robot service is provided here. The documented API is a local JavaScript library included with this website. It does not make network requests.
On ArmAPI.com, the phrase describes a virtual claw’s control and state interface. The practice cabinet has deterministic hit regions, no money, and no real rewards. It is separate from physical robot control.
Try the playground, read the robot arm API beginner’s guide, then use the documentation to inspect the same local state model.
A little code. A lot to explore.
Start in the browser. Understand the interface. Build with clearer boundaries.