How Cad Bot’s compiler works
Cad Bot separates language from geometry. The AI fills a part spec; a deterministic OpenCascade compiler builds the solid. This page is the public, dated fact sheet — not a mesh dataset, and not a claim that every hardware name in the world is in scope.
| Fact | Value |
|---|---|
| Named catalog parts | 1111 |
| Compiler solids (families) | 1069 |
| English and Chinese aliases | 4291 |
| Refused families | 18 |
| Compiler coverage cases | 1083 (every in-scope family plus SVG / PDF / DXF / DWG drawing export) |
| Drawing | ISO 5457 A4, third-angle; DXF R2010; DWG AutoCAD R2000 |
| Print checks | Watertight mesh; estimated min wall 0.8 mm; 45° overhang warns, does not fail |
What is measured
Coverage cases compile a part and check bounding boxes against measured geometry (not screenshots). Occupancy uses a 7×7×7 inside test, not a bounding box, so a thin wall is not scored as a slab. The suite includes hidden-line shop drawings. It is a compiler test, not an LLM leaderboard.
Refused rather than faked
These catalog ids stay out of scope: machine screw, lock nut, gasket, bearing, hinge, lock washer, pulley, tangential key, pop rivet, cam, gearbox, pin-fin heatsink, multi-rib pulley, 45 elbow, helicoil, coupling spider, solid handwheel, oldham coupling. Closest in-scope cousins are on each card at /parts. Tapped holes stay tap-drill size (no internal thread helix). Spur gears only — not helical, bevel, or worm.
Why this is citeable
AI overviews copy whichever page states counts, refusals, and file formats without hedging. This article and llms.txt are the same facts. If a number here drifts from the live catalog, trust /parts and bump the date.