RoboSelect360

Showing 25 of 28 from the live probe.

• Semiconductor layer status

  Health of the SEMICONDUCTOR layer: profiles loaded, semiconductor signal counts, load errors. One status tool per layer - the three report different layers, not the same server.

• Robot catalogue (semiconductor filters)

  List the robot catalogue with filters, including semiconductor tier and payload. Returns the same catalogue as the mechanical and software variants - call one, not three. Pick this one to filter by semiconductor tier.

• Robot profile (semiconductor coverage)

  Commercial profile of one robot (specs, pricing, viability score), plus whether a semiconductor teardown exists for it. The commercial fields are identical in all three get_robot variants - the layer flag is the only difference.

• Signal feed (semiconductor)

  List semiconductor supply chain, performance and operational signals across the panel, with filters. Panel-wide, not per robot: requires an access right on at least one robot.

• Robot signals (semiconductor)

  Active supply chain signals affecting one robot's semiconductor BOM. Requires an access right on the robot requested.

• Block analysis (semiconductor)

  Analyse one functional block of the semiconductor layer, for a single robot at a time. Requires an access right on the robot named, or on at least one robot when none is.

• Compare robots (semiconductor)

  Compare 2 to 5 robots side by side on semiconductor BOM, metrics, risk and geographic exposure. Requires an access right on EVERY robot listed; if one is missing the call returns a refusal naming it, and compares nothing.

• Semiconductor dependency profile

  Geopolitical and supply chain dependency analysis for one robot, built on its semiconductor BOM: geographic concentration, single-source exposure, export control. Requires an access right on the robot requested.

• Semiconductor BOM teardown

  Semiconductor bill of materials for one robot: functional blocks, components, suppliers. Requires an access right on the robot requested; without it the call returns a refusal naming that robot.

• Mechanical layer status

  Health of the MECHANICAL layer: mechanical profiles loaded, mechanical signal counts, load errors. One status tool per layer - the three report different layers, not the same server.

• Robot catalogue (mechanical filters)

  List the robot catalogue with filters, including mechanical-profile status and payload. Returns the same catalogue as the hardware and software variants - call one, not three. Pick this one to filter on mechanical coverage.

• Robot profile (mechanical coverage)

  Commercial profile of one robot (specs, pricing, viability score), plus its mechanical-profile status. The commercial fields are identical in all three get_robot variants - the layer flag is the only difference.

• Signal feed (mechanical)

  List mechanical supply chain, performance and operational signals across the panel, with filters. Panel-wide, not per robot: requires an access right on at least one robot.

• Robot signals (mechanical)

  Active supply chain signals affecting one robot's mechanical BOM. Requires an access right on the robot requested.

• Block analysis (mechanical)

  Analyse one mechanical block (actuation, structure, energy, perception), for a single robot at a time. Requires an access right on the robot named, or on at least one robot when none is.

• Compare robots (mechanical)

  Compare 2 to 5 robots side by side on mechanical BOM, specifications, risk and geographic exposure. Requires an access right on EVERY robot listed; if one is missing the call returns a refusal naming it, and compares nothing.

• Mechanical dependency profile

  Geopolitical and supply chain dependency analysis for one robot, built on its mechanical BOM: geographic concentration, critical raw materials, single-source exposure. Requires an access right on the robot requested.

• Mechanical BOM teardown

  Mechanical bill of materials for one robot: motors, reducers, screws, bearings, batteries, structure, wiring. Requires an access right on the robot requested; without it the call returns a refusal naming that robot.

• Software layer status

  Health of the SOFTWARE layer: software profiles loaded, software signal counts, load errors. One status tool per layer - the three report different layers, not the same server.

• Robot catalogue (software filters)

  List the robot catalogue with filters, including software tier and software-profile status. Returns the same catalogue as the hardware and mechanical variants - call one, not three. Pick this one to filter by software tier.

• Robot profile (software coverage)

  Commercial profile of one robot (specs, pricing, viability score), plus its software tier and profile status. The commercial fields are identical in all three get_robot variants - the layer flag is the only difference.

• Signal feed (software)

  List software supply chain signals across the panel, with filters. Panel-wide, not per robot: requires an access right on at least one robot.

• Robot signals (software)

  Active supply chain signals affecting one robot's software stack. Requires an access right on the robot requested.

• Block analysis (software)

  Analyse one software block (OS, middleware, runtime, control, fleet), for a single robot at a time. Requires an access right on the robot named, or on at least one robot when none is.

• Compare robots (software)

  Compare 2 to 5 robots side by side on software BOM, TCO, jurisdiction exposure, lock-in and export control risk. Requires an access right on EVERY robot listed; if one is missing the call returns a refusal naming it, and compares nothing.