Open Source RoboticsRobots, software & learning

Onshape Robotics Toolkit

Software

Onshape Robotics Toolkit provides programmable robot-assembly parsing, graph/model handling and export through Onshape's REST API. [1] [2] [3] [4] [5]

Installation & first result →Official websiteGetting started

For
Robotics developers investigating the named source configuration [1] [2] [3] [4] [5]
Source rights
Named licenses are documented by part. Review licenses
Unknowns
operating system, compute requirements not fully established. Review gaps

Source researched · Not tested by us
Sources checked · Research details

Licenses & related hardware

Requirements · Research details and dates

On this page

Overview

Onshape Robotics Toolkit provides programmable robot-assembly parsing, graph/model handling and export through Onshape's REST API. It is distinct from a released robot design or an offline CAD editor. Its README identifies inspiration from onshape-to-robot; this entry covers the separate Python API and model/export implementation rather than treating one tool as a drop-in replacement for the other. [1] [4] [5]

Is this for you?

Known limitations
  • Librarycode permissiondoesnotgrantOnshapeaccess or inputCAD/vendorpart rights.
  • Exportexample containsrealassemblyURL/configpaths; noAPImutation/export orgeometry validation here.

Editorial assessment of cited source; no runtime or hardware test.

[1] [2] [3] [4] [5] · Editorial assessment

What you need

Dependencies
  • Package0.6.0 literalPythonrequirement>=3.10,<=3.13; model/REST/graph/geometrydependencies
  • Onshapeaccount/APIcredentials andaccessibleassembly; optionalsimulationextra separate

[1] [2] [3] [4] [5]

Installation & first result

Open the upstream getting-started guide [1] [2] [3] [4] [5]

  • Inspect the named configuration, source interfaces and required external components.
  • Attempt only the matched documented workflow after resolving environment and rights gaps; no operation reproduced here.

Editorial assessment of cited source; no runtime or hardware test.

[1] [2] [3] [4] [5] · Editorial assessment

Installation

Package 0.6.0 metadata requires Python >=3.10,<=3.13; Onshape account/API access and secret keys plus accessible assembly are needed for the selected programmable export; simulation extra is separate.

Documented source requirements/route, not installation or compatibility reproduced by this catalog.

[1] [3] [5]

Project notes

Match package metadata before installation

The inspected pyproject.toml declares version 0.6.0 and the literal Python requirement >=3.10,<=3.13. That upper bound should not be silently broadened to every future or patch-level interpreter without checking package resolution. Base dependencies include requests, pydantic, numpy/scipy, geometry/XML and graph libraries; simulation dependencies are a separate extra. No dependency environment was installed. [3]

The export example uses ORTConfig, Client, CAD, KinematicGraph, Robot and URDFSerializer, with an environment-file path, an assembly URL, maximum depth and output/mesh paths. The README requires an Onshape account and access/secret API keys. The selected examples/export/main.py uses .env, loads ORT.yaml when present, sets MAX_DEPTH=2, writes output/robot.urdf and selects custom_meshes. Those are example settings to inspect or replace, not universal requirements or credentials for another person's assembly. Select an accessible assembly and inspect configuration before making REST calls or adapting programmatic design operations. No API request or CAD modification was made. [5]

Exported structure still needs robot-specific validation

The sampled Robot implementation represents links/joints and serialization-related model handling. An exported URDF does not establish that frames, inertia, geometry or actuation match the intended physical robot. When mass properties are missing, the sampled source substitutes mass 1.0, zero center of mass and identity inertia; it also supplies joint-limit defaults when neither configuration nor API limits are available. Inspect these values for the selected robot rather than assuming they were measured. Treat the selected model and external simulator as separate validation boundaries; no geometry comparison, simulator load or hardware-control test occurred here. [4]

The actual pinned license file is LICENSE.md with Apache-2.0 terms; a badge or link spelling is not a substitute for that file. Service access, source CAD, vendor parts and external assets retain their own rights. No benchmark or superiority over another converter was tested. [1] [2]

What we checked

Pinned source/document inspection only; no installation, compile, credentials/API use, simulator, lab experiment or physical hardware test.

Not yet established

  • Requirements: operating system, host computer
  • Version-specific hardware compatibility (ecosystem tags alone do not establish it)

Updates

Upstream last updated
Not established
Latest release
Not established
Profile updated
Nov 1, 2026
Sources last checked
Nov 1, 2026
Next review
Dec 1, 2026
Reviewed revision
f4cedbd

Source files and licenses

Concrete scoped robot-facing software/research workflow, not complete manufacturing or verified operational behavior.

LayerAvailability / license
softwareavailable · Apache-2.0
Selected source availability/notice only; external hardware, models, data and dependencies have separate rights. No blanket redistribution or operational clearance. [1] [2] [3] [4] [5]
documentationavailable · Apache-2.0
Selected source availability/notice only; external hardware, models, data and dependencies have separate rights. No blanket redistribution or operational clearance. [1] [2] [3] [4] [5]

No separate physical design, pretrained distribution or dataset is selected as the released contribution in this scoped software review.

References

Each source links to the exact revision we read. “Used for” shows where this page relies on it.

Correction guidance · Discussion is not enabled · Profile format 0.7.0-draft.5

Change history