How Gradient Dynamics fits togetherΒΆ
The central API/MCP service is the source of truth for engineering operations. Studio, REST, the Python client and MCP agents use it to create geometry, mesh, simulate and inspect saved results.
Stage |
What you create or inspect |
Next decision |
|---|---|---|
Design |
Imported CAD or an editable implicit document |
Are dimensions, regions and requirements correct? |
Geometry |
Verified surface/volume exports and provenance |
Is the representation suitable for meshing? |
Mesh |
Structured or Hex-core cells, boundaries and quality |
Is the resolution and quality adequate for the physics? |
Fluxcore |
A saved simulation request and durable job |
Did the solve meet the stated convergence standard? |
Results |
Histories, fields and engineering quantities |
Is the evidence adequate for the design decision? |
A project organizes collaborative work and revisions. An API/MCP workflow can also begin privately without an existing project. Artifacts retain identity and lineage across entry points, so you can resume work without recreating it.
Start with the Studio quickstart, REST quickstart, MCP connection or first implicit body.