Mesh2Metal API for CAD Manufacturability Checks

Mesh2Metal API gives engineering and procurement software a code-level path to manufacturability checks, illustrative pricing, and lead-time estimates. Run a check when CAD changes in CI, inside a generative-design loop, or before a purchase request. Free access covers about 100 checks per user per day once accounts open.

The Mesh2Metal API creates a consistent gate between CAD changes and the next engineering or purchasing decision. A single integration can request a manufacturability verdict, receive clear reasons, and obtain an illustrative price and lead-time estimate without making a person repeat the same early review by hand.

Three common patterns fit the API:

A failed result should be actionable. If a design cannot be made, Mesh2Metal explains why and points toward a practical correction. Use the manufacturability overview for the broader review criteria, then use the API when those checks need to run repeatedly.

An API check can carry file metadata, a geometry summary, material, and quantity. Supported CAD formats include STL, STEP/STP, 3MF, and OBJ. A code integration can pass the metadata already held by a revision system alongside the summary needed for an early geometry review.

The exact API contract will be provided with access. The following request and response are illustrative, not a promise of final field names or values:

{
  "file": {
    "name": "bracket.step",
    "format": "STEP",
    "bytes": 284391,
    "sha256": "illustrative-digest"
  },
  "geometry": {
    "boundsMm": { "x": 120, "y": 80, "z": 24 },
    "volumeCm3": 31.4,
    "surfaceAreaCm2": 228.6,
    "featureCount": 14
  },
  "material": "Aluminum",
  "quantity": 2
}

An illustrative response might look like this:

{
  "verdict": "pass",
  "reasons": [
    "illustrative: geometry meets the selected review rules"
  ],
  "price": {
    "amount": 185,
    "currency": "USD"
  },
  "leadTimeDays": 3
}

The example shows the shape of an automated handoff: metadata and geometry go in, while a verdict, reasons, price, and lead-time estimate come out. The quote page remains the place to confirm the current commercial result and exact date.

The API verdict is an early engineering signal, not a substitute for the release review required by your product. A pass means the submitted inputs fit the selected review rules. A result that needs attention identifies the relevant geometry or requirement. A failed result should tell the team what to change before another check.

Lead-time estimates depend on part size, material, quantity, and the final review. Mesh2Metal supports quantities from 1 to 200 and part sizes up to 800 × 800 × 600 mm, with larger parts considered on request. Use the lead-times page for planning context. Use materials and the quality overview when a design decision depends on material or documentation.

The access model is simple:

• Free access covers up to approximately 100 checks per day per user.
• An account is required for API access.
• Accounts open soon. Join the waitlist to be notified when access is available.
• The API overview is intentionally high level; schema details and access instructions follow when the account path opens.

For tool-oriented development, Mesh2Metal also has an MCP overview. Teams can keep a code-based check in CI and use a tool-based check during design review, with the same goal: find issues early and make the next decision clearer.

CAD analysis can run client-side in the browser. Browser-based analysis means source geometry can stay on the visitor device instead of leaving it for an initial manufacturability check. That is useful when a designer wants to test a concept before sharing the underlying file with a service.

Automated integrations should still define their own data-handling rules, access controls, and retention policy. Please don’t send us export-controlled (ITAR/EAR) technical data until we have set up a compliant path with you — contact us first.

Start with one representative part and one decision: block a CAD revision, retain a generative-design candidate, or create an early purchasing estimate. Record the request inputs and response reasons so the team can see why a revision passed or failed. After the account path opens, connect that check to your existing CI or procurement step, then use the how it works guide and contact page for the next discussion.

Set up API → Try it out now joins the waitlist.