Hi,
I reached out after hearing a common concern from robotics engineers:
“Why would I upload my URDF/Xacro to an external service?”
That hesitation makes complete sense especially with proprietary robot models.
So just to clarify how RoboInfraapi is designed:
-
Files are processed in-memory and never stored
-
No training or reuse of uploaded data
-
No persistence of URDF/Xacro/3D files
-
Requests are isolated via API keys
The goal is simple:
add CI/CD-style validation for robot models without exposing your data
To give a concrete example, I tested RoboInfraapi with a public NASA humanoid model Robonaut 2:
https://github.com/gkjohnson/nasa-urdf-robots/blob/master/r2_description/robots/r2c6.urdf
It validates structure, detects issues, and analyzes kinematics instantly the same pipeline teams can run in CI.
Why teams use it:
-
Catch URDF issues before simulation/debugging
-
Standardize Xacro → URDF across environments
-
Validate models automatically in GitHub Actions
-
Avoid “works on my machine” ROS inconsistencies
You can try the public validator here (no signup required):
https://roboinfra-dashboard.azurewebsites.net/validator
If you’re open to it,
I’m happy to:
-
walk through the architecture
-
or help test it on one of your models (privately)