rigyd
SDK + CLI for Rigyd: convert any 3D model, text prompt, or image into a physics-enabled SimReady simulation asset — USD for NVIDIA Isaac Sim, MJCF for MuJoCo — from your terminal or your Python code.
Zero dependencies. pip install rigyd and go.
CLI
pip install rigyd
rigyd login # stores your rgyd_live_... key
rigyd generate --text "wooden chair" --export isaac -o ./assets
rigyd generate --image front.png --image right.png --image back.png --image left.png
rigyd convert chair.glb --tris 50000 --export all
rigyd jobs list
rigyd jobs get <job_id>
rigyd download <job_id> --export mujoco # re-download any job, 0 credits
rigyd simulate <job_id> --scene drop # physics demo video, 0 credits
rigyd whoami # user + credit balance
--exporttakes a format (usd,mjcf,all) or a simulator alias (isaac→ USD,mujoco→ MJCF). Default:usd.- Progress goes to stderr, the result path to stdout, so it composes:
blender $(rigyd convert scan.obj --export usd). Add--jsonfor a machine-readable manifest (agents/CI).
| Input | Command | Cost |
|---|---|---|
| Text prompt | rigyd generate --text "..." |
2 credits |
| 1 or 4 images | rigyd generate --image ... |
3 credits |
3D file (.glb/.gltf/.fbx/.obj/.stl/.ply/.usd*) |
rigyd convert FILE |
1 credit |
Python SDK
import rigyd
rigyd.configure() # key from login/env
job = rigyd.convert(prompt="a wooden dining chair")
job.wait(on_progress=lambda j: print(j.status, j.stage, j.progress))
xml_path = job.download(fmt="mjcf") # or "usd" / "all"
print(rigyd.account()) # user + credit balance
MuJoCo extra
pip install "rigyd[mujoco]"
model = rigyd.load_model(prompt="a wooden chair") # -> mujoco.MjModel, ready to mj_step
Loading into a live simulator
- NVIDIA Isaac Sim — use the Rigyd SimReady Importer extension
(Omniverse Community Registry:
rigyd.simready) to generate and load assets onto the stage without leaving the app. This CLI produces the same USD files for offline/scripted pipelines. - MuJoCo —
rigyd.load_model(...)above, ormujoco.MjModel.from_xml_path(<path from rigyd download --export mujoco>).
Configuration
Key resolution order: --api-key flag → RIGYD_API_KEY env →
~/.config/rigyd/config.json (written by rigyd login, mode 600).
License
MIT — see LICENSE.
Metadata
Release files for rigyd 1.0.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| rigyd-1.0.1.tar.gz | 15.9 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| rigyd-1.0.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 33.6 kB
Release files / rigyd-1.0.1.tar.gz
| Download URL | rigyd-1.0.1.tar.gz |
|---|---|
| Size | 15.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
5479c1f26c9deabd4f9aa24bf9400fba5a426cd41177244d4bf4a994b2cc768d
|
|
BLAKE2b-256 checksum How to use checksums |
4db44a52a44a6baa4a603d69f06152ee4566ee4c7fd67b864be2bf210038c4da
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.13
|
Release files / rigyd-1.0.1-py3-none-any.whl
| Download URL | rigyd-1.0.1-py3-none-any.whl |
|---|---|
| Size | 17.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
e2e44f67b6bcd6225cf08daf1470f6c57e43a29b1156c16b99e7c7ee04081f71
|
|
BLAKE2b-256 checksum How to use checksums |
48e296a9defbd524bdf4a50658c68ae7165d28af6b34c2f7ee5f0d6260d8f402
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.13
|