A robot is a record on your account: a name, one key, and a list of the policies it may connect to. You make the robot first, then say what it connects to. Its code holds the key and names the policies, never the robot: the key says which robot it is.
Make a robot
On the console’s Robots page, New robot makes one and the robot’s Policies tab says what it may connect to. From the command line:
# everything ending in _user is yours # the robot, and its key, printed this once seq robot create arm_1_user # what it may connect to seq robot set arm_1_user policies=pick_user,place_user
seq robot list shows every robot you have, offline ones too, and how many your plan allows;
seq robot show <name> shows one, and what it is doing now
(the seq CLI).
Its key
A robot has one key, made with it and shown once. It starts seq_robot_, and it may connect to the
policies on the robot’s list and call the models they declare, nothing else
(Keys). It has no expiry and no spending limit.
The one thing to do to a key is replace it: seq robot key <name>, or Replace key on the
robot’s Settings tab. A new key is made and shown once; the old one stops at once, and anything connected
with it is cut off until it connects with the new one. seq robot rm <name> deletes the robot
and its key, and cuts it off the same way.
A robot key made before robots came is a robot now, with that key’s policy on its list, and nothing about it has to change. It keeps the expiry it had until it is replaced; its robot’s Settings tab shows it.
Its list
The list is the policies this robot may connect to. seq robot set <name>
policies=<p1>,<p2> sets all of it: what you leave out comes off. Every name has to be one of
your policies; otherwise nothing changes, and the error says which name it was.
- A policy not on the list is refused with a
403whosedetails.reasoniskey_bound, andsequence-ai’s error names the command that adds it. teleopgoes on the list as a policy does. It lets a person drive the robot (Teleoperation); it holds no machine and is not billed.- A policy you take off the list goes on until the robot’s connection to it next renews, and is refused then.
- Deleting a policy takes it off every list. The robots and their keys stay.
seq policy status <policy>says which robots list that policy.
Connect
connect() takes the names of policies on the robot’s list. One name returns one handle, as it
always has; several return a tuple, in the order you named them. Which one acts is your code’s choice
(Run).
pick_user, place_user = sequence_ai.connect(
"pick_user", "place_user", api_key=ROBOT_KEY_user)
Each policy you connect holds a place on a worker, and that worker is billed while it runs, whether your code calls it or not: connect only the names you use.
Your own key (seq_dev_) connects to any of your policies by name, as a quick test. That is not a
robot: it has no list and is not on the Robots page.
Record
The platform stores none of a robot’s steps. Its Record is a switch that lets you record them yourself:
seq robot set <name> record=on, or the switch by its name in the console, and then
seq robot record <name> writes them to a file of yours as they come
(Field data).
How many
An account may have 10 robots on Starter and 200 on Team; a Custom plan starts at Team’s and can be set for
the account. The Robots page shows how many you have. One more than that is refused with a 409 whose
details.reason is robot_limit: delete one first. An account already over its limit
keeps its robots and makes no new ones. A robot itself costs nothing; what it connects to is billed as any
policy is (Pricing).