Standard, Gentle, and Attentive define the first Motius Robotics behavior catalog for service and public-facing robots.
Motius Roboticsrobot behavior layer
Behavior layer
PROFILEADAPTERRUNTIMEMOTION
Robot behavior layer for service robots.
ROBOTBEHAVIORLAYER
Install reusable interaction profiles for service and public-facing robots.
Motius Robotics makes the same robot feel standard, gentle, or attentive across navigation and object interaction without rewriting the controller underneath.
Hotel-service robotics is the first visible wedge, not the whole category.
Object handover, approach-and-stop, and push object already show the same robot behaving differently without changing the task plan.
The first buyer is the vendor, fleet operator, or deployment partner who already feels behavior mismatch property by property.
Why now
Service robots are scaling.Behavior still gets rebuilt site by site.
Hotel delivery, reception, and public-service deployments already exist. What is still missing is a reusable behavior layer above the controller, so the same robot does not need to be retuned property by property.
professional service robots sold in 2024
hospitality robots sold in 2024
RaaS fleet growth in 2024
How it works
Behavior becomes reusable software before it becomes a bigger platform.
Motius Robotics starts with a narrow product surface: define the interaction profile, validate the visible difference, and map it into the runtime boundary without rewriting the controller.
01profilescene fitbehavior surface
Define a profile
Choose the interaction style the robot should carry in this service setting.
Motius Robotics turns robot behavior into a reusable software surface instead of leaving it buried in scene-by-scene tuning.
Profile surface: Standard / Gentle / Attentive
02same robotsame tasksdifferent feel
Prove the difference
Keep the same robot and task plan while making behavior visibly different.
The current proof already spreads across handover, approach-and-stop, and push object. What changes is the behavior profile, not the task plan.
Current proof: 3 interactions on one robot
03timingspacingsafe bounds
Map it into runtime
Translate profiles into motion without replacing the runtime underneath.
Motius Robotics lives above the controller. Adapters convert profile traits into timing, spacing, smoothing, hold duration, and finish quality while hard limits stay below.
Boundary: profile -> adapter -> runtimeParticipate
Two product surfaces can already go live.
Motius Robotics can open one surface for service-reference contribution and one surface for profile commerce. Both can start now without pretending the full network is finished.
Contribution flow
Upload service reference videos.
Contributors can record short service interactions, add behavior tags, and push the clip into Motius Robotics's reference intake for review and training use.
Upload a short clip from phone or field recording
Tag the behavior: handover, approach, wait, corridor etiquette
Send the file into the Motius Robotics reference queue
Profile commerce
Reserve and buy behavior profiles.
Operators can choose a profile pack, select token or x402 as the intended payment rail, and place an order before fulfillment is turned on.
Choose Standard, Gentle, or Attentive
Select token or x402 purchase intent
Reserve now, fulfillment later when delivery opens
Core profile set
Three profiles define the first Motius Robotics catalog.
They are not marketing labels. Each profile resolves into explicit execution fields and scene behavior for service robots.
Behavior signatureNeutral / direct / efficient
Neutraldirectefficient
Profile 01
Standard
Neutral, direct, and efficient. Built for service settings where the robot should feel clear, dependable, and operationally straightforward.
Interaction toneNeutral / direct / efficient
Motion traitsShorter pause, tighter spacing, quicker completion
Behavior signatureWarm / patient / soft
Warmpatientsoft
Profile 02
Gentle
Warm, patient, and calm. Designed for situations where the robot should feel less abrupt and more reassuring before, during, and after the interaction.
Interaction toneWarm / patient / soft
Motion traitsLonger pause, wider stop distance, softer finish
Behavior signatureAlert / polished / social
Alertpolishedsocial
Profile 03
Attentive
Alert, polished, and socially readable. A profile for robots that should feel presentation-ready in public service settings and hospitality environments.
Interaction toneAlert / polished / social
Motion traitsCleaner arrival, brighter cadence, composed exit
Current proof
Three visible interactions, one behavior layer.
Current footage already covers navigation and object manipulation on the same robot. What changes is not the task plan, but the interaction profile carried through it.
Same robot
Validation layerThe proof keeps one robot body and one filmed setup while switching only the active interaction profile.
Three interactions
Proof spreadCurrent footage already covers navigation and object manipulation: object handover, approach-and-stop, and push object.
One profile boundary
Product layerThe visible differences come from the behavior layer, not from rewriting the task plan or replacing the runtime underneath.
Object manipulationVisible difference in rhythm, hold, and finish softness
Close paceHold durationExit softness
Interaction 01
Object Handover
The handover sequence stays fixed. The active profile changes closing speed, hold duration before release, and how the robot exits the exchange.
StandardStandard / faster close / shorter hold / more direct release
GentleGentle / slower close / longer hold / softer exit
NavigationVisible difference before any object exchange happens
Braking timingStop distanceSettle calmness
Interaction 02
Approach And Stop
The target zone stays fixed. The active profile changes braking timing, personal distance, and how calmly the robot settles near a person before contact happens.
StandardStandard / later brake / tighter stop / quicker settle
GentleGentle / earlier brake / wider stop / softer settle
Object manipulationVisible difference in smoothness and end-state control
Contact smoothnessMovement paceFinish control
Interaction 03
Push Object
The object task stays fixed. The active profile changes contact smoothness, movement pace, and how the robot finishes the interaction around the object.
StandardStandard / direct contact / shorter finish hold
GentleGentle / softer contact / smoother finish hold
Reading the proof
What the current demo already shows.
The video is intentionally narrow. It is showing whether a profile change becomes visible before contact, during the interaction, and after the interaction.
How to read the current clip
Current proof already spans object handover, approach-and-stop, and push object.
The clip is not trying to prove general robot intelligence. It is showing that one robot can keep the same tasks while visibly changing the interaction feel through Standard and Gentle profiles.
Actual proof clipOne robot, three visible interactions
Object handover, approach-and-stop, and push object all stay on the same robot body while the active interaction profile changes how the motion feels.
Current status
What already exists today.
A working prototype, a behavior-layer story, and multi-interaction proof already exist. What does not exist yet are signed pilots or revenue.
Working prototype
A product thesis, behavior-layer framing, and installable profile story already exist in working form.
Multi-interaction proof
Current footage already shows one robot behaving differently across three visible interactions.
Pre-revenue
No signed pilot yet. The next step is to turn this proof into the first hotel-service deployment path.
Runtime and rights
The product works without token. The rights layer does not.
Behavior becomes motion through the adapter layer. If profiles later move across creators, operators, and fleets, the rights layer matters separately from the product itself.
FieldStandardGentle
speed_scale1.000.82
pause_ms200420
approach_distance_m0.800.95
end_effector_smoothing0.900.96
Core capabilities
Product, systems, and validation aligned around one wedge.
Motius Robotics is being built as a robotics software product first, with one clear boundary across product framing, runtime integration, and live robot validation.
Product layer
Behavior product framing
Motius Robotics is being shaped as a software layer first: profiles, proof, contribution flows, and deployment surfaces all read as one product boundary.
Runtime layer
Systems and adapter boundary
The runtime work stays focused on translating behavior profiles into bounded motion without replacing the controller underneath.
Validation layer
Robot-side proof and deployment
Live validation stays tied to real robot execution, service reference intake, and the first deployable behavior surfaces.
Why Motius Robotics
Motius Robotics starts by turning behavior into reusable software, so the same robot can fit more human environments without being rebuilt from scratch.
The current proof already shows the layer becoming legible. The next step is to carry that behavior standard across more service environments, more deployments, and eventually more capable service robots.