Standard Bots combines industrial arms with AI programming and vision

Standard Bots sells industrial robot arms with visual programming and AI skills for locating parts, inspecting work and assisting routine creation. Its published starting prices are the beginning of a manufacturing-cell budget, with tooling and commissioning still to scope.

01 / ProductHardware, operating software and AI in one offer

Standard Bots makes industrial robot arms and the software used to program them. Its current product range includes Spark, Core and Thor, with different payload and reach classes. It also lists Bolt as private beta. That status matters: a buyer comparing available arms should not plan a production rollout around a development product without confirming access.

The AI offer is concrete enough to separate into jobs. On its AI page, Standard Bots describes an agent that helps create and change routines, Locate for finding parts with a camera, and Inspect for checking parts against taught examples. These features address programming and perception. They do not make tooling, workholding or a safe machine interface disappear.

Standard Bots OS supports block-based routines, basic moves, logic and input/output conditions, as well as programmatic control through APIs. The same page labels creating and distributing custom no-code AI skills as coming soon. Existing routine assistance and that future authoring capability should therefore be evaluated separately.

The appeal is a shorter connection between the person who knows the manufacturing process and the system that executes it. A machinist can explain a sequence without becoming a specialist robot programmer. The engineering responsibility remains: the sequence must respond correctly to the actual machine, fixture, part and exception state. Accessible programming changes how a cell is configured, not whether the cell needs commissioning.

02 / AudienceStart with the manufacturing constraint

The strongest candidate has a specific repeated job and an identifiable constraint: a machine waits for loading, finished parts need sorting, or visual checks create a queue. Standard Bots' machining material focuses on loading and unloading equipment, including CNC applications. A useful buyer brief starts with the machine and part flow rather than the desired robot model.

Payload includes more than the workpiece. The end effector, adapters and handling method influence the usable envelope, while the fixture and door arrangement influence reach. The Core specifications list an 18 kg payload and 1.3 m reach. Those figures help shortlist equipment; they do not establish that every 18 kg component can be handled in every orientation or at your target speed.

A high-mix shop should examine changeovers as closely as steady production. Cameras can help when parts arrive in different positions, but recognition quality, grasp access and placement still need evaluation for the actual parts. A buyer needing an immediately available mobile generalist should keep Bolt's private-beta status visible. For a conventional cell, start with the currently offered arm and a supported application.

03 / WorkflowA proposed machine-tending acceptance workflow

This proposed pilot uses one machine and one part family; it is not a deployment we performed. Map the full cycle from incoming stock to accepted finished part. Record the machine-ready signal, loading position, door state, cycle-complete signal, unloading destination and rejected-part route. Document which events must stop the process and which can be retried safely.

Next, ask an applications engineer to match the arm and tooling to the actual layout. Standard Bots' order form requests the application, timing and operational details such as parts, machines, volumes and shifts. Provide those facts early. A short video of the work can communicate reach and handling constraints, but it should supplement measured dimensions and an agreed process description.

Build the simplest routine that completes the agreed cycle. Use blocks or AI assistance for moves and logic, then inspect what was generated. Test each input/output transition independently before relying on a combined sequence. In particular, verify that a stale machine-ready signal cannot start an unsafe or duplicate action. Plain-language editing is useful only when operators can recognize and explain the resulting behavior.

Introduce the variability that matters: different part positions, an empty input tray, a misloaded item and a machine that does not finish on schedule. For vision-based handling, include the lighting and surface conditions found on the floor. Measure accepted parts per shift and operator interventions, with changeover time recorded separately. This distinguishes improved automation from a demonstration that hides its setup effort.

Finish with an operator handover. Someone on each shift should understand how to stop, inspect, reset and resume the cell, and which faults require vendor support. The acceptance record should include the final routine, equipment configuration and tested recovery cases. That gives the factory a maintained process instead of a program that only its original author understands.

04 / PricingStarting prices are a hardware comparison

The current public range displays starting prices of $29,500 for Spark, $39,500 for Core and $49,500 for Thor. These are dollar-denominated starting figures on the U.S.-focused site; the displayed page does not explicitly label the currency code. Confirm USD, taxes and regional terms in the quotation. They are not a published price for a complete commissioned application.

The commercial inquiry leads to an application discussion rather than an immediate checkout for a fully specified cell. Ask which camera, controller, base, gripper, software features and support terms the proposal includes. Clarify installation and machine integration. An available wrist camera, for example, should not be silently treated as included merely because the product can support it.

Calculate value from the constrained process. If the machine already waits for upstream material, faster tending may not increase shipped output. If labor is reassigned, identify the useful work that becomes possible. Include the time spent teaching a new part, handling rejects and maintaining tooling. This creates a more realistic comparison between a modest cell improvement and a larger factory automation project.

05 / DistinctionsWhy the software matters as much as the arm

Standard Bots brings graphical routines, natural-language help and API control into the same offer. That gives different users different entry points: operators can work with visible steps while developers can integrate more specialized logic. The practical distinction is whether a routine can remain understandable when it grows beyond the first demonstration. Ask to review an example that includes real faults and changeovers.

The company's AI skills separate locating from inspecting. Finding a part answers where it is and how to approach it; inspection asks whether it meets an appearance criterion. They may share a camera but require different acceptance data. A system that can reliably find shiny metal in a tray has not thereby demonstrated that it detects every defect relevant to your quality process.

ABB is a relevant comparison when the buying decision spans broader industrial automation and integration. Path Robotics provides a more focused comparison for adaptive welding. Neither comparison should reduce to which company uses AI most often in its marketing. Match the supported process, tooling, programming ownership and service model to the job you need completed.

06 / QuestionsAvailability and safety remain application-specific

Keep three states distinct in a proposal: currently supplied capability, private beta and coming soon. The current pages assign Bolt to private beta and custom no-code skill creation/distribution to coming soon. If either is essential, obtain a supported delivery commitment before making it a dependency. A roadmap feature should not quietly explain the economics of a present-day purchase.

The Core page uses collaborative-operation language, but whether a particular cell can operate without additional guarding depends on the application. Sharp parts, hot material, machine doors and end effectors can create hazards beyond the arm itself. Ask the integrator and site safety owner to assess the complete installation and its stop behavior. Product positioning alone cannot settle a site's risk assessment.

Public pages do not establish inspection accuracy, every supported gripper combination or the recurring price of every AI capability. Request tests with your defect examples and specify what happens to uncertain results. For software changes, agree who can edit production routines, how changes are approved and how a working version is restored. These controls protect the usefulness of accessible programming as more people begin using it.

07 / DecisionBuy a working cell with an understandable routine