PRODUCT

Four Cad

Four Cad is a CAD reasoning workspace powered by Rowe 1.0. The workbench ingests OBJ, STL, and point-cloud JSON in the browser, can proxy native CAD files to a hosted converter, converts geometry into Rowe spatial input, and returns renderable reasoning scenes with issues, comparisons, improvements, visual overlays, measurements, and grounded explanations.

Upload

Add OBJ, STL, or point-cloud JSON in the Four Cad workbench. Native CAD formats use the converter route when configured.

Analyze

Four Cad converts geometry into Rowe point_cloud_scene input and runs spatial reasoning through the dashboard runtime.

Inspect

Review reasoning_scene.v2 overlays, issues, measurements, comparisons, geometry changes, and grounded text.

Where Four Cad fits

Four Cad is the product workspace. Rowe is the model API underneath. API docs stay focused on Rowe request and response contracts; Four Cad docs describe the CAD workflow built on those contracts.

Open Four Cad →Read Rowe API docs →

Current support

The browser path is live for OBJ, STL, and JSON point-cloud scenes. Native CAD files are accepted by an authenticated converter boundary and require a hosted geometry kernel configured with environment variables before they return real geometry.

Supported browser uploadsOBJ, STL, JSON

Parsed in the browser and converted into Rowe point_cloud_scene input.

Native CAD converterSTEP, IGES, SLDPRT, SLDASM

POST /api/dashboard/four-cad/convert proxies native CAD files to FOUR_CAD_CONVERTER_URL when configured.

Workbench route/dashboard/four-cad

Authenticated dashboard product surface for upload, analysis, comparison, visualization, and report export.

Run route/api/dashboard/four-cad/run

Authenticated dashboard route that sends the generated Rowe request through the existing spatial response runtime.

Primary outputreasoning_scene

Renderable 3D reasoning data with objects, relations, overlays, measurements, issues, comparisons, and geometry changes.

Generated Rowe request

Four Cad sends Rowe the same spatial input shape you can send to the Responses API directly. Uploaded geometry becomes grouped point-cloud objects with stable object ids and CAD metadata tags.

Terminal

{
  "model": "rowe-1.0",
  "input": {
    "task_type": "optimize",
    "object_id": "candidate-bracket",
    "secondary_id": "baseline-bracket",
    "detail": "standard",
    "goal": {
      "product": "Four Cad",
      "mode": "compare",
      "objective": "Compare the first two CAD parts, find geometry issues, and suggest improvements."
    },
    "point_cloud_scene": {
      "scene_id": "four-cad-compare",
      "point_clouds": [
        {
          "object_id": "candidate-bracket",
          "kind": "box",
          "tags": ["cad_upload", "baseline_model"],
          "points": [{ "x": 0, "y": 0, "z": 0.45 }]
        },
        {
          "object_id": "baseline-bracket",
          "kind": "box",
          "tags": ["cad_upload", "candidate_model"],
          "points": [{ "x": 0.08, "y": 0, "z": 0.45 }]
        }
      ]
    }
  }
}

Native CAD converter

Configure FOUR_CAD_CONVERTER_URL and optionally FOUR_CAD_CONVERTER_TOKEN to proxy STEP, IGES, SLDPRT, and SLDASM files to a hosted converter. Without that configuration, the route returns converter_required with HTTP 501.

Terminal

curl https://fourechelon.com/api/dashboard/four-cad/convert \
  -H "Cookie: <dashboard session cookie>" \
  -F "file=@assembly.step"