For robot companies
Sell robots, not integrations.
Robots fail at a building’s handoffs: the elevator, the badge reader, the fire alarm. Plynth gives your fleet one API to all of them, run by each building’s own agent.
from plynth.client import RobotClientimport uuid robot = RobotClient(url, robot_id, secret)trip = str(uuid.uuid4()) # a new ID for each trip robot.request(trip, "door") # OPEN_COMMANDED: go throughrobot.report(trip, "passed") # PASSED: done
Five minutes to your first ride
Read the docs →01
Get a test key
One click on the docs page, no sign-up.
Get a test key →02
Download the kit
Python 3.9 or later, nothing to install.
curl -sO …/robot-kit.zip03
Check your key
Whose robot it is, whether its clock is right, and which doors and elevators it may use.
python3 -m plynth.hello04
Ride the building
A door, an elevator ride, refusals, notices and emergency drills, and what passed.
python3 -m plynth.conformance
01
One API
Your fleet connects once. We keep the adapters to each elevator maker and badge system.
02
Rehearse every failure
Refusals, timeouts, fire recall and lost connections come back as reason codes. The sandbox has a door or elevator that fails each way, so your robots handle them before any site visit.
03
Live on the record
Each building’s owner chooses your route and accepts your robots from its own record: unassisted trips, days counted, interventions per 100 trips.
The sandbox
Your first ride takes five minutes.
A test key in one click, then a simulated building: an elevator bank, a badge door into a server room, and doors that fail on purpose.