Revit
BIM & documentation
The documentation and BIM-data workhorse. Archi Automate composes Revit API operations for schedules, parameters, views, sheets, and code checks.
The bridges
Each bridge speaks its host's native API, so the assistant works with the real model — not a lossy export. Add a bridge and every workflow you already wrote gains a new endpoint.
BIM & documentation
The documentation and BIM-data workhorse. Archi Automate composes Revit API operations for schedules, parameters, views, sheets, and code checks.
Design & BIM
Where design and BIM meet. Drive zones, GDL objects, layouts, and model data through the Archicad API in the same plain language.
Geometry & NURBS
Free-form geometry and computational design. Read and build NURBS, meshes, and Grasshopper-ready definitions for facades, structure, and form-finding.
Open BIM exchange
Read and write IFC models directly — vendor-neutral. Archi Automate opens an .ifc file as a live bridge, so the assistant can query, validate, and federate openBIM data alongside the authoring tools.
Vectorworks · Tekla · SketchUp
The bridge architecture is uniform. New hosts join the same AI surface — your prompts, skills, and guardrails carry straight over.
The category-defining difference
Most AEC automation is locked to one tool and one fixed list of commands. Scripts, macros, Dynamo or Grasshopper graphs are excellent when the workflow is known in advance and lives inside a single application — but real projects span Revit, Archicad, Rhino and IFC at once, and most work is one-off.
Archi Automate takes a different approach. You describe the outcome in natural language. The connected AI inspects the live model in whichever host you point it at, composes the required native API operation, previews it in dry-run, and executes approved tasks inside the host's own transaction model.
The result is intelligence that moves with your project — across tools, not trapped inside one.
What you can do
The same AI surface that answers a one-line question moves data between tools and runs a project-wide workflow — each operation inside the host's own transaction model.
Ask questions of a live Revit, Archicad, Rhino, or IFC model — categories, parameters, geometry, relationships — without schedules or scripts.
Which rooms in the Archicad model have no zone category assigned?
Translate geometry and data across hosts with intent preserved — not a lossy export. Archi Automate maps source to target through each native API.
Rebuild this Rhino massing as a Revit mass family with matching levels.
Run compliance, naming, and integrity checks against codes like TEK17 — and cross-check one model against another for consistency.
Flag every door that exists in Revit but is missing from the Archicad set.
Architecture in Archicad, structure in Rhino, documentation in Revit — one assistant keeps the shared data aligned as each discipline moves.
Sync the structural grid from Rhino into the Revit and Archicad models.
Describe logic spanning categories, parameters, conditions, and several hosts. Archi Automate composes the operations and runs them in order.
For every facade panel in Rhino, create a Revit curtain panel and tag it.
Per-role read/write modes, scope limits, deletion rules, and audit retention — applied uniformly across every bridge and every seat.
Architects: read-only. BIM leads: dry-run. Director: unrestricted.
Interoperability
The bridges share one AI core, so data and intent move in any direction. The assistant reasons over the source model and composes native operations on the target — no manual round-trip.
Revit
BIM & documentation
Archicad
Design & BIM
Rhino
Geometry & NURBS
openBIM (IFC)
Open BIM exchange
More
on the roadmap
Archi Automate core
MCP · skills · guardrails · audit
The approved massing and facade logic lives in Rhino. Archi Automate reads the NURBS surfaces and rebuilds them as native Revit mass families, levels, and curtain systems.
design intent preserved, not flattened in a lossy export
Read the room schedule and department data from the Revit model, and write matching zones with the same names and categories into the Archicad project.
one source of truth, two coordinated models
Pull the building envelope and storey heights from Archicad into Rhino as clean reference geometry, ready for daylight, energy, or structural study.
analysis on live data, not a stale export
Multi-modal inputs
Voice, images, drawings, spreadsheets, regulation PDFs, external APIs — whatever your AI client can read, Archi Automate can ground in the live model of any connected host.
Voice
Voice input through compatible AI clients turns spoken instructions into native operations — hands free, mid-meeting, in any connected host.
“Show every column in Rhino that clashes with a Revit beam.”
Images
Hand the AI a site photo, a sketch, or a precedent image. It reads the visual, grounds it in the model, and composes the next step.
“Match the window rhythm in this facade photo on the south elevation.”
2D drawings
Feed in 2D PDFs, DWG snapshots, or annotated markups. The AI extracts intent and maps it onto the live model in any host.
“Tag every door on this consultant's fire-strategy markup.”
External data
Excel, GIS, manufacturer catalogues, energy-model results, building-code databases, your own APIs — wired in through the AI client.
“Pull the latest equipment-load table from the consultant SharePoint.”
No ceiling
Each host API is vast. Every category, parameter, view, object, and transaction primitive across Revit, Archicad, Rhino, and IFC. A fixed-command plugin exposes a sliver of one of them. Archi Automate exposes the whole surface of each — composed on demand, in plain language, subject to your policy.
And the system grows in two directions. Add your studio's skills — naming conventions, templates, typology rules, regulation packs — and add new bridges as they ship. As the underlying LLMs get smarter, every workflow you've built gets smarter with them. No migration.
Example prompts
Each prompt runs against live models through MCP — read-only, dry-run, or transactional. The same surface that handles one host coordinates two.
Take the approved tower massing in Rhino and rebuild it in Revit as a mass family with floors at each storey height, then report the gross floor area per level.
Compare the Revit and Archicad sets and list every door that exists in one model but not the other, with its level and fire rating.
Read the room schedule and department parameter from Revit and create matching zones in the Archicad model, keeping names and categories aligned.
Cross-check every habitable room on Level 03 against TEK17 §12 daylight and ventilation rules, and produce a punch list of the non-compliant rooms.
How it works
The whole chain is inspectable. You can swap the AI client, pin the policy, or replay any session from the JSONL audit log.
Your existing chat with Claude, GPT, or any MCP-compatible client. No new UI to learn.
Claude · GPT · MCP→Open MCP transport carries the request to the Archi Automate core. Standard, inspectable, swappable.
open protocol→Selects the right bridge, composes the native API operation, and checks it against your active policy and skills.
policy · skills · dry-run→Executes inside the host's own transaction model — Revit, Archicad, Rhino, or IFC — with rollback on error.
Revit · Archicad · Rhino · IFC→Safety & guardrails
Archi Automate can compose operations across each host's API surface, subject to your active guardrail policy. You set the boundary; the core enforces it the same way on Revit, Archicad, Rhino, and IFC.
Inspect any element, parameter, or relationship in any connected host. The bridge refuses any write operation, regardless of what the AI tries.
The AI composes the operation, but execution stops at a diff. You see exactly what would change — in either model of a cross-tool flow — and decide whether to commit.
Write operations run inside the host's own transaction model with rollback on error. Every step is logged, on every bridge.
Every composed operation is screened against a configurable deny-list before execution. Every session writes to a JSONL audit log, regardless of host.
Inside the app
Archi Automate runs as a quiet desktop app beside your authoring tools. A handful of screens — bridges dashboard, guardrails, and AI-client setup — cover the entire operator workflow across every bridge.

DashboardRevit 2027, Archicad 29, Rhino 8 and openBIM (IFC) — all bridged.
Modular by design
Archi Automate is a layer, not a product with a fixed scope. Layer in your studio's naming conventions, template libraries, typology rules, regulation packs, or conversion mappings — and the AI combines them with each host's native API.
Skills and guardrails are written once and apply across every bridge. As new bridges ship and the underlying LLMs get more capable, the system you deploy today gets quietly more useful — with no migration.
Ship your studio's number/letter conventions as a skill the AI applies in every host automatically.
Wrap your view templates, sheet layouts, and Archicad master layouts so the AI uses them, not generic defaults.
School, hospital, office, residential — encode the rules of thumb that govern each typology.
TEK17, IBC, NBC, fire codes — distil regulations into checks the AI can run against any model.
Define how your studio maps geometry and data between tools — Rhino layers to Revit categories, and back.
Anything you can describe in a doc, you can package as a skill. The AI picks the right one for the task and host.
Compatibility
Any MCP-capable AI client can drive Archi Automate, and every bridge speaks its host's native API. Bring the assistant you already use.
2025–2027298IFC4 · IFC2x3roadmapopen specx64supportedbothindirectVersus
Dynamo, Grasshopper, and macros stay excellent for known workflows inside one tool. Archi Automate covers the rest — the one-off tasks, the validations, and the moves between tools that don't have a script yet.
| Capability | Platform scripts | Single-tool AI plugin | Manual IFC round-trip | Archi Automate |
|---|---|---|---|---|
| Plain-language input | ○ no | ◐ partial | ○ no | ● yes |
| Works across Revit, Archicad, Rhino & IFC | ○ no | ○ no | ◐ partial | ● yes |
| Read from one tool, write to another | ○ no | ○ no | ◐ partial | ● yes |
| AI composes the operation on demand | ○ no | ○ no | ○ no | ● yes |
| No manual export / import round-trip | ● yes | ● yes | ○ no | ● yes |
| Dry-run preview before commit | ○ no | ◐ partial | ○ no | ● yes |
| Configurable guardrail policy | ○ no | ◐ partial | ○ no | ● yes |
| Audit trail of every session | ○ no | ○ no | ○ no | ● yes |
| Grows as new bridges ship | ○ no | ○ no | ○ no | ● yes |
Learn & support
Get the most out of your Archi Automate subscription — step-by-step guides, an active forum, and silent-install tooling for IT.
Choose topics, find answers, get step-by-step instructions, and develop your skills with the full user guide.
User GuideThe Archi Automate Forum is the place to ask questions, find answers, learn from experts, and share your knowledge.
Archi Automate ForumRoll out Archi installers across multiple machines with the Silent Installer Guide, built for fleet deployment.
Silent Installer GuideArchi Collection gives you Archi Automate plus the rest of archi's Revit workflow toolkit, expanding workflow coverage while offering better value than licensing plugins one by one.
Buy
Archi Automate
14-day full-featured trial. Every bridge, guardrails, dry-run, and cross-tool flows included. Works with the AI client you already use.