Skip to content
Tallyfy
Developers

Boston Dynamics Spot, Stretch and Atlas

How Spot inspections could feed a Tallyfy procedure

Section titled “How Spot inspections could feed a Tallyfy procedure”

Boston Dynamics makes Spot ↗[1], a robot that walks a site and checks equipment. Other software can tell Spot to run an inspection ↗[2] and read what it found. A written procedure in Tallyfy could take over from there, so a problem the robot flags becomes a task with an owner and a deadline.

Tallyfy doesn’t sell that connection. Your team would have to build it.

What Boston Dynamics makes today

Section titled “What Boston Dynamics makes today”

Boston Dynamics has three robots in its portfolio ↗[3], and software called Orbit.

Boston Dynamics’ review of Spot’s customers ↗[9] counts more than 1 million automated data captures in 2023. It names many customers, among them these four. National Grid piloted Spot at a high-voltage site where no people can go during operation. AB InBev used Spot at a brewery to cut average repair times from a few months to 13 days. UKAEA sent Spot into Chernobyl with a radiation detection payload. In 2023, Purina used Spot’s data for predictive maintenance.

What outside software can ask Spot to do

Section titled “What outside software can ask Spot to do”

Through Orbit’s API1, a program can do the following, as of October 2026:

Since release 5.1, Spot can also pause, redirect or end a mission based on what it sees ↗[15], with no operator needed.

What outside software can’t do yet

Section titled “What outside software can’t do yet”

All four limits are as of October 2026.

  • None of Orbit’s documented webhooks ↗[16] fires when a whole mission ends. They fire once per action, so a program has to ask Orbit for the run’s status.
  • The parts you’d use most can break. Runs, schedules, webhooks and work orders sit in a tier Boston Dynamics calls “experimental/beta” ↗[17], and it may make breaking changes there in any release.
  • We found no public developer docs for Stretch or Atlas. The developer site ↗[18] covers Spot and Orbit.
  • No MCP interface is documented yet. Boston Dynamics says release 5.2 “lays the foundation for a new MCP layer” ↗[19]2 that would let AI agents deploy Spot. We found no MCP documentation on its developer site.

Where a written procedure in Tallyfy fits

Section titled “Where a written procedure in Tallyfy fits”

Spot can find a problem. People still have to fix it. A Tallyfy template is the written procedure for that fix: the steps, who does each one, and by when.

As a concept, Orbit’s alert would go to a small connector your team writes. The connector would call Tallyfy’s API to launch the matching process and fill in its kick-off form. Tallyfy would then assign the repair and the sign-off to named people. Once the repair is done, a Tallyfy webhook could tell the connector to send Spot back for a second look.

Boston Dynamics describes a similar pattern itself: an application that creates a work order in an asset management system ↗[20] whenever the robot identifies an anomaly.

Concept: a Spot alert becomes a tracked Tallyfy taskSpot runs a checkOrbit flags an alertYour connectorTallyfy processAssigned task Sends readingSends webhookCalls Tallyfy APIAssigns work

What to notice:

  • Orbit keeps running the robot. Tallyfy would only track the follow-up work.
  • The dashed box is the one piece your team would build and look after.
  • One alert on one action starts the process.

Technical details

Section titled “Technical details”

(Skip this unless you’re setting up the technical side.)

Section titled “Related articles”

Integrations > Robotics

Tallyfy has no integration or partnership with any robot maker. This concept section shows how a…

Footnotes

Section titled “Footnotes”

  1. A way for other software to talk to Orbit directly, sending instructions and reading data with nobody at a screen. ↩

  2. MCP (Model Context Protocol) is the shared standard that lets AI assistants connect to outside tools. ↩

Get in touch
About Tallyfy