Blog · Guide · 29 Sep 2026 · 3 min read

Can AI drive Autodesk Inventor? A guide for steel fabricators and design offices

Inventor can be controlled from outside, with scripts written and run by an AI agent. What that means in practice, what you need, what stays with the designer, and where it goes wrong.

Inventor is not only driven with a mouse. It has had a programming interface (API) for years: an outside program can open a file, read the parts, create the drawings, export DXF and PDF. Until now you needed a programmer. Today an AI agent can write the script, and the designer tells it what to do in plain words.

What an AI agent is, in plain terms

It is a program that works on your computer. You write "for every part in this assembly, make the drawing with the thickness in the title block". It writes the script, runs it, opens the files it produced and checks that the result is what you asked for. If it is not, it fixes the script and runs it again.

It is not a chat that gives advice. It does the work. We use Claude Code, by Anthropic.

How it connects to Inventor

Three routes, depending on the job:

• External script. It attaches to a running Inventor and drives it: open, export, rename, save. Good for batch work across many files.
• iLogic rule. Code that lives inside Inventor and runs there. Good for drawing creation, where views, dimensions and the title block matter.
• Reading the produced files. DXF and PDF can be opened and measured without Inventor. This is the check.

The agent writes all three. The designer never touches code.

An example: from STEP to cutting drawings

1. The STEP file arrives with every part inside, often with no names and no bill of materials.
2. Reading the model. For each part: flat plate, bent plate, round bar or commercial section, and at what thickness.
3. The register. One sheet, one row per part: code, thickness, material, quantity. It is the single source: drawings are made from it.
4. The drawings. An iLogic rule generates all of them from the register.
5. The DXF files for the cutting machine, exported in one batch.
6. The check. The DXF files are opened and compared with what the register says should be inside.

Questions people ask us

So it does everything by itself? No. Decisions stay with the designer: materials, which parts can be merged, what is cut from sheet and what is bought. The agent does the repetitive work and the checks.

Does it make mistakes? Yes, and it makes them confidently. That is why no result counts until it has been checked inside the file. A "done" message is not proof. A dimension read from the DXF is.

Do I need to know how to code? To use it well you need to know what the output must be: a correct drawing, a standard plate thickness, a quantity that adds up. That is the designer's trade, not the programmer's.

Do I need a special computer? The one that already runs Inventor, with its licence.

Do my drawings stay confidential? The files stay on your computer. What the agent reads, though, is sent to the AI model to be processed. If a customer forbids their data leaving the building, say so first.

Isn't a draughtsman faster? On one part, yes. On hundreds of different parts, no: that is where the time goes into repeated steps, and the errors are the careless kind, like a mistyped thickness. A rule does not get tired.

The technical guides

• Drive Inventor from the terminal without an MCP server
• Run an iLogic rule from outside Inventor
• Export DXF and PDF with a script
• Inventor API errors and what they mean

Where to start

With a repetitive job you already do and know well: DXF export, title blocks, the parts list. If the result can be checked, it can be automated.

If you want to know whether this fits your work, send us a file: we will tell you what can be done.