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
Python 3.9 or later. Nothing to install, no sign-up.
Your own robots, drills and a sign-in for your team: ask for your own keys.
1Get a test key, and download it as
plynth-sandbox.env.2Download the kit
$cd ~/Downloads && curl -fsSO https://sandbox.plynth.build/docs/robot-kit.zip && unzip -qo robot-kit.zip && cd robot-kit3Check your key
$python3 -m plynth.hello --env ../plynth-sandbox.env4Ride the elevator and go through the door
$python3 -m plynth.conformance --env ../plynth-sandbox.env
One API
Your fleet connects once. We keep the adapters to each elevator maker and badge system.
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.
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.
Streets, too
Between buildings, the same API asks the city: WALK at the crosswalk, a curb held for a pickup, closures before your robot reaches them.
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.