Put it behind a button in the tool people already use.
The same work, triggered from where the job actually starts. A row in your CRM, a file landing in a folder, a form somebody submits.
You want this to happen without anyone opening a new tool.
$ pip install cadmould$ python feasibility.py --stl enquiry.stl
What that looks like
A virtual environment, one browser sign-in, and two installs. The sign-in points this environment’s pip at the licensed wheel; nothing else is hidden.
$ python3 -m venv .venv$ source .venv/bin/activate$ pip install --upgrade pip cadmould-sdk-auth$ cadmould-sdk-auth$ pip install ".[examples]"
Then check it took
$ pip install ".[result-viewer]"$ python examples/result-viewer/scripts/08_result_viewer.py
That one runs offline against a result that ships with it, so it works before any account does.
Want the scaffolder output, how authentication resolves and what the agent context files hold?
The commands in fullWe are reworking how they reach you, so for now work from the copy that shipped with your licence. It holds the same use cases, the same docs and the same context files, and every command above applies inside it.
What you can ask for
A Python SDK, installed with pip
One login configures the index, one more command installs it. Meshing, upload, materials and running a simulation are all wrapped.
A plain REST API for everything else
Projects, groups and the decision log are HTTP, so build a client in whatever your stack already speaks.
Worked pipelines to lift from
The gate study and the design-space campaign each ship a few hundred lines you can take wholesale rather than start from a blank file.
This is the only page here that assumes you write software. Everything it describes is also reachable from the other two routes, without any of it.
Start with something real
Every use case is a worked job you can point at your own part. Take one as it stands, then say what is different about yours.