The Genworks stack is not one SKU. It is a ladder: open-source Gendl for learning and experimentation, hosted professional workflows taking shape online, commercial Genworks GDL for serious development and deployment, and royalty-based arrangements where closed-source distribution is the real need.
Gendl is the AGPL-licensed kernel at the heart of everything else. Pair it with Basalt — our free, open-source deployment stack, with the Readymacs console — for the most direct way to learn the language, explore live objects, and build open-source applications. This is the right entry point for hobbyists, researchers, students, and anyone who wants to understand the stack before making a commercial commitment.
For many professional engineers, the preferred path is increasingly online rather than installed: browser entry, hosted terminals, MCP access, guided examples, and a cleaner upgrade path into paid capability. That experience is still being built out, but it is an explicit product direction rather than an afterthought.
Now live: metered geometry API
The first pay-per-call resource is the NACA airfoil CAD export: any NACA 4- or 5-digit airfoil, or a family of up to twelve, as clean NURBS curves in STEP (AP203) or IGES, built on demand by Genworks GDL on the SMLib geometry kernel. No account and no API key: the endpoint answers HTTP 402 with an x402 payment requirement, an agent or script with a funded wallet pays in USDC on Base, and the file comes back on the retry. Prices are per request and follow what the request asks for: three cents for one airfoil, eight for a family; for the gear, one cent for the drawing numbers alone, three for an outline, five for a meshed pair, fifteen for a solid and twenty-five for a pair of solids. Every 402 quotes the exact price. A bad request is answered 400 with the reason, and nothing is charged unless the file is served. Every STEP file's header records the resource and the parameters it was built from, and every result can be traced: the resource's free /trace path is a verification record stating the standards the geometry follows, the checks made on every result, the derived numbers for a given request, and, for the demos we publish as open, the source itself; add trace=1 and the JSON report and the STEP header name it.
GET https://genworks.com/demo/naca-nurbs/cad?digits=2412
GET https://genworks.com/demo/naca-nurbs/cad.igs?digits=0012,2412,23012&chord=250
digits one NACA code, or a comma-separated family (max 12)
chord scale factor, default 1
points samples per airfoil, 50-500, default 216
tolerance NURBS approximation tolerance, 0.0001-0.01
format step | iges (or use /cad.stp, /cad.igs)The second resource is the involute spur gear: ISO 21771 geometry with the flank from the base circle and the root fillet the basic rack's tip generates, profile shift and backlash, as a planar outline or an extruded solid, a meshing pair at the working center distance, and the drawing numbers (pitch, base, tip and root diameters, tooth thickness, span over k teeth, contact ratio) as JSON. An undercut request is refused with the profile shift that fixes it.
GET https://genworks.com/demo/gear/cad?module=2&teeth=20
GET https://genworks.com/demo/gear/cad.stp?module=2&teeth=20&mate=40&face_width=10
GET https://genworks.com/demo/gear/cad.json?module=2&teeth=20&mate=40
teeth 6-200 (required) module mm, default 1
pressure_angle degrees, default 20 shift profile shift x
face_width mm: the solid mate a mating gear's teeth
backlash mm format step | iges | jsonAny x402 v2 client works, for example the @x402/fetch package for Node with an EVM signer. Humans keep the free interactive demo in the browser. Need a resource we do not offer yet, such as a gear profile, a lofted wing, a standard beam section, or a STEP conversion? Tell the wishlist: a free GET of /demo/geometry/wishlist?want=... records the ask, and the next resources are chosen from that list.
Coming soon
Hosted KBE sessions, more metered geometry resources on the same door, and clearer online package combinations for professional evaluation and VAR-style offerings.
Genworks GDL builds on the same declarative core with commercial Lisp, support, and optional industrial modeling components. Today the most obvious commercial shapes are development-oriented seats, enterprise deployment seats, and royalty-based arrangements for some closed-source distribution cases.
Best for development teams who need closed-source work, commercial support, and a stable foundation for serious prototyping or internal tools.
Best for on-site deployment, runtime distribution, SMLib-backed geometry, CAD interfaces, and the traditional installed commercial model that many organizations still require.
If your main need is closed-source distribution rather than installed enterprise seats, the royalty path may be a better fit than the legacy seat model.
The engines run in a free, open-source deployment stack we maintain: Basalt, the container deployment; Readymacs, the Emacs console; and Lisply-MCP, the layer that puts an AI agent in the running image. A deployment's ingress and dashboard roles are filled by commercial binaries, licensed separately.
Start with open-source if you are learning, with royalties if you need closed-source distribution, with hosted direction if you want online professional evaluation, and with Enterprise if you need installed commercial deployment.