Dimvo

API

Integrate structured STEP analysis into quoting, ERP or engineering workflows.

Use versioned geometry, recognized feature data and manufacturing evidence in your own part records and review tools. Private beta access is arranged directly, by request.

Request API accessTry the Analyzer →

Private beta · access by request

Choose the response family your integration needs.

The current input is STEP geometry: AP203, AP214 or AP242 in a .step or .stp file. The analysis describes supported geometry and observations; it does not interpret a drawing’s tolerances, surface-finish callouts or process instructions.

PartAnalysis

dimvo.part-analysis.v1

Normalized geometry and topology, quality and availability information, recognized holes, face references and available manufacturing evidence. Use it to enrich a part record or support an engineering review.

WorkspaceAnalysis

dimvo.workspace-analysis.v1

Wraps the part analysis with visualization and face-linked geometric evidence for interactive inspection. The display mesh uses the same analysis-local face IDs as the semantic data.

Inspect two real response excerpts.

Both snippets are explicit projections of the same clean-room blind-hole response. Fields are omitted for readability; no product values are invented. Normalized hole and reach measurements are in millimetres; coverage values are ratios.

PartAnalysis · real response excerpt
{
  "schema_version": "dimvo.part-analysis.v1",
  "features": {
    "holes": {
      "count": 1,
      "items": [
        {
          "id": "hole-1",
          "type": "blind",
          "nominal_diameter": 16,
          "total_depth": 10
        }
      ]
    }
  },
  "accessibility": {
    "scope": "zero_radius_straight_line_3axis_v1",
    "status": "available",
    "estimated_maximum_geometric_reach_mm": 86
  }
}
WorkspaceAnalysis · real response excerpt
{
  "schema_version": "dimvo.workspace-analysis.v1",
  "analysis": {
    "schema_version": "dimvo.part-analysis.v1",
    "accessibility": {
      "schema_version": "dimvo.accessibility.v1",
      "scope": "zero_radius_straight_line_3axis_v1",
      "candidate_orientations": [
        {
          "rank": 1,
          "direction": "+X",
          "direct_coverage_ratio": 0.8925155413647806,
          "incremental_coverage_ratio": 0.8925155413647806,
          "cumulative_coverage_ratio": 0.8925155413647806
        },
        {
          "rank": 2,
          "direction": "+Z",
          "direct_coverage_ratio": 0.7073549717664648,
          "incremental_coverage_ratio": 0.1074844586352193,
          "cumulative_coverage_ratio": 1
        }
      ]
    }
  },
  "visualization": {
    "schema_version": "dimvo.visualization.v1",
    "status": "available"
  }
}

Download the example STEP → · Inspect its real workspace →

Response fields and evidence

Selected paths below are relative to WorkspaceAnalysis. Its analysis object contains PartAnalysis. Feature and mesh references belong to that response and must not be matched across separate analyses.

analysis.geometry
Bounding geometry, volume, surface area and available centres.
analysis.features.holes
Recognized hole types, dimensions, segments and source face IDs.
analysis.faces.items
Analysis-local face IDs, surface type, adjacency and available geometric parameters.
analysis.accessibility
Cartesian straight-line access, geometric scope and explicit availability.
analysis.accessibility.candidate_orientations
Ranked candidate directions with direct, incremental and cumulative coverage ratios.
analysis.accessibility.estimated_maximum_geometric_reach_mm
Estimated geometric reach in millimetres; not a required cutter length.
visualization.mesh
Server-generated display mesh, with triangle groups linked to analysis-local face IDs.

A typical integration flow

  1. Agree access and scope

    Describe your quoting, ERP or engineering workflow, expected volume and required response family. Integration details are agreed during private beta.

  2. Submit a STEP part

    Send geometry through the agreed integration and associate the response with the correct part and revision in your system.

  3. Validate the response

    Check schema versions and availability states before using measurements. Keep normalization units and geometric scope with the data.

  4. Present evidence for review

    Store supported semantic results or render the workspace. Connect feature and access observations to their source faces before making process decisions.

Versioned schemas and availability

  • Part, workspace, accessibility and visualization carry their own schema versions.
  • Respect explicit status and unavailable reasons. Missing or null evidence is unavailable, not zero.
  • A display mesh may be unavailable while semantic part data remains useful.
  • Read normalized units from the response and retain the source-unit information when relevant.

Current analysis limitations

  • Recognized feature data currently covers supported hole types, not every possible feature.
  • Cartesian access is geometric evidence, not a complete machinability or collision guarantee.
  • Candidate orientations are not validated physical setups. Geometric reach is not cutter length or holder clearance.
  • Machine, fixture, tool and shop context, automatic process plans and production approval are outside the current scope.