02Platform quickstartFirst platform run

Teach your agent to call the solver.

One script, the entire loop: mesh the part locally, upload the geometry, choose a material, run AI filling, read the peak cavity pressure. Every later example is this loop repeated with a decision wrapped around it - get it working once and the rest is arithmetic.

Swap the bundled STL for your own and it is your part, in about fifteen minutes. The result is written viewer-ready, so example 01 opens it without conversion.

Hand this to your agent

Read the platform quickstart at toolkit.simcon.ai and set it up in this folder, following the setup page it links to. Then run one filling simulation on the bundled part and report the peak cavity pressure.

Platformcadmould.cloud SDK~ 5 minOne browser login

The loop

Watch one run go through

This is the actual sequence the example runs, at the speed it happens. Everything after the first login is unattended.

Your agent writes the code. You decide whether the result makes sense.

run_filling.py

Ready0.0 s

Mesh locallyThe STL becomes a solver mesh on your machine, inside the licence session.

Upload once, reference by idGeometry is data. Every later run points at the same id.

Pick a materialFrom the platform catalogue. The card carries the full physics of the grade.

Run AI fillingThe call returns the finished simulation. No polling loop to write.

Download and readPeak cavity pressure printed, and a viewer-ready result on disk.

Run it

Scaffold, install, run

The first platform call opens a browser once for the login. After that there is no token to manage.

From nothing

$ pip install ".[cloud-quickstart]"$ python examples/cloud-quickstart/run_filling.py

Output lands in build/ - the meshed part and the result file.

Two things worth knowing

Never nest licence sessions

Meshing and the platform calls belong in the same Session.user_based(). An inner session releases the licence when it exits, and the outer work then fails in a way that looks like an entitlement problem. Pass manage_session=False to helpers that would open their own.

SI units throughout

Temperature in K, pressure in Pa, lengths in mm, flow in cm³/s - the same contract on every endpoint. If your own code works in other units, convert once at the edge and range-check there, rather than carrying two conventions around.

Units across the API · temperature K · pressure Pa · spatial mm · flow cm³/s

SDK or your own client

Both paths are supported. This one is the default.

Stay on `cadmould.cloud`

It wraps the per-simulation surface - geometry, materials, running a filling simulation, downloading the result - and handles the login. For one-off runs and most automation, nothing else is needed.

Build your own over REST

Reach for this when you need the management surface - projects, groups, the decision log - or want to pin things the SDK does not expose. Examples 03 and 04 take that path, in any language you like.

Next: put a decision around the loop

One run answers nothing on its own. Example 03 runs many and scores them into a gating decision.

Gate study All examples