Request data
- Millimetre request on a 0.001 mm grid
- Equivalent decimal-inch request
- Boxes, quantities, clearance, and representative arm geometry
- Optional inch display projection
Developer Preview ยท Working examples
Call RotoSpider from your usual tools.
Run the same known request from Python, JavaScript, curl, or PowerShell. Each client calls the public RotoSpider layout WebAPI.
Inside the package
Four clients, two equivalent requests
Client programs
- Python 3 standard-library client
- Node.js 18+ client with built-in fetch
- curl shell script
- Windows PowerShell / PowerShell 7 client
- AI-agent scheduling workflow notes
Run after extracting
Use the client for your environment
python python/layout_check.py node javascript/layout_check.mjs bash curl/layout_check.sh powershell -ExecutionPolicy Bypass -File powershell/layout_check.ps1
Set ROTO_API_URL to use the same clients with an agreed private or local endpoint. Pass sample-request-inch.json to see decimal-inch input and the optional inch display projection; canonical result fields remain physical millimetres.
Current status
A working preview, not a frozen production contract
Active iteration
These examples work with the current public layout API, but the schemas and examples may change as they are tested against real rotomolding operations. Check the response api field and agree versioning before production integration.
Bring the factory specifics
Useful inputs include arm and spider geometry, mold master data, cycle and changeover times, compatibility rules, daily capacity, and MOM or ERP mappings.
The public RotoScheduler scheduling interface is still being shaped with rotomolders. This package demonstrates the RotoSpider layout call and does not claim that a public scheduling contract is fixed.