Products

One runtime.
Two ways to reach it.

Engineering files are not text. Flatten a drawing into a caption and the geometry — the B-rep solids, the dimensions, the tolerances, the constraints — is gone before the model ever reasons about it. So the answers come back plausible and unusable.

Rowe keeps the geometry. Your STEP, IGES, DXF, PDF, or SVG file is parsed into a structured cad_scene — solids, faces, entities, dimensions, annotations — and the model reasons over that. You get typed JSON back: measurements, relationships, issues, and comparisons, each traceable to the geometry it came from.

Four Echelon
extraction, spatial reasoning, API, and deployment.
Four Cad
upload, inspect, compare, and export.
Rowe 1.0
structured scene in, typed reasoning and evidence out.

What works today

STEP / STP
3D solids, faces, exact volumes
IGES / IGS
3D solids and surfaces
DXF
2D entities, dimensions, annotations
PDF
Vector drawing entities and annotations
SVG
Vector drawing entities
OBJ / STL / JSON
Point clouds and meshes, browser-side

What does not

SolidWorks native (.sldprt / .sldasm)
Export to STEP and upload that. The API returns HTTP 415 — deliberately, not as a bug.
Latency SLAs
The status page reports single-probe latency samples. We do not publish p50/p99 guarantees.
Head-to-head accuracy claims
We publish our own eval methodology and error bars. We do not claim to be best, superior, or state of the art.
Draw.io and other diagram formats
There is no parser and no normalized contract for them today. On the roadmap, not shipped.

Start with one call.

Get a key, send a file, read the JSON. Pricing is a $49.00/month base plus metered spatial tokens, and only successful requests bill.