What to expect in alpha
As an alpha user you’re working with software that is real and functional, but not yet polished:- Rough edges exist. You may encounter unexpected generation results, UI quirks, or export issues. This is expected and normal.
- Fast iteration. The team ships updates frequently. Features, prompts, and behaviors can change week to week.
- Direct feedback loop. Your bug reports and feature requests go straight to the engineers building Gizmo. You’ll often see fixes or improvements turn around quickly.
- No uptime SLA. The service may be briefly unavailable during deployments or infrastructure work.
- Limited asset history. Storage and versioning features are still being built — export and save your assets locally as you go.
How to request access
Access to Gizmo is gated during alpha. To request an account:Send an access request email
Email viswajit@antimlabs.com with the subject line “Gizmo alpha feedback or API access”.
Describe your use case
In the body of your email, briefly describe what you’re building and which simulator you’re targeting (NVIDIA Isaac Sim, MuJoCo, or both). This helps the team prioritize onboarding and tailor support.
Wait for your credentials
The team will review your request and send you account credentials or an invitation link. Response times vary during alpha — expect a reply within a few business days.
Sign in and start generating
Once you have credentials, go to gizmo.antimlabs.com, sign in, and follow the Quickstart guide to generate your first asset.
Early API access
Gizmo exposes a REST API that lets you generate physics-ready assets programmatically — useful for batch workflows, CI pipelines, or integrating asset generation into your own tooling.The API is not publicly documented yet. During alpha, API access is granted on a case-by-case basis to users with specific automation needs.
- Email viswajit@antimlabs.com with the subject “Gizmo alpha feedback or API access”
- Include a short description of your intended use case (e.g., batch asset generation, CI integration, custom tooling)
- The team will provide an API key and point you to the current endpoint reference
Providing feedback
Your feedback is the most valuable thing you can contribute during alpha. The team wants to hear about:- Bugs — unexpected behavior, generation failures, export errors, UI issues
- Quality issues — assets that don’t match your description, incorrect joint structures, poor geometry
- Feature requests — capabilities you wish existed, simulator integrations, workflow improvements
- General impressions — what’s working well and what isn’t