PRIVATE PILOT · IFC WORKFLOWS

Give AI a language
for building models.

Turn IFC into editable BIR text. Compile changes back into IFC with a report of what changed and what verification established.

For developers building BIM and MEP tools. Bring your own AI; HouseIR handles the model translation and scoped checks.

01 / SOURCEIFC modelYour existing building data
02 / EDITBIR + residualAI-editable text + preserved source
03 / COMPILEIFC + reportChanges, checks and limitations

A SMALL INTERFACE. A SERIOUS CONTRACT.

Your AI proposes the edit.
HouseIR checks the result.

01

Read without losing the source

Convert IFC into BIR text and a signed residual. The residual retains source information outside the editable representation.

02

Write with visible boundaries

Check language and references before compilation. Supported edits are checked for preservation, schema regressions and strict sub-millimeter geometry.

03

Refuse what cannot be proved

Unsupported geometry or failed verification returns a diagnostic. A failed compile does not provide a successful IFC artifact.

Verification is scoped to supported representations and operations. It does not certify engineering design, code compliance or universal BIM/MEP coverage.

EVIDENCE, WITH ITS LIMITS

Built around
testable guarantees.

We are expanding real-file and MEP evaluations before claiming broader pilot support. Each pilot starts with agreed models, operations and acceptance criteria.

78 passed 0 failed · 0 skipped

Latest frozen-release targeted evaluation · October 4, 2026 · 55.88 seconds. The full suite and broader corpus evaluation are still pending.

  • Exact semantic preservation and text round trips
  • Identity and placement checks for tested edits
  • Strict geometry checks for supported shapes
  • API isolation, failure and recovery tests
  • Scripted straight-pipe edit preserving identity and endpoint ports

Download the synthetic MEP demo →

A scripted edit extends a straight pipe from 1,000 to 1,400 mm while preserving its GlobalId, ports, system and neighboring element. This demonstration does not use AI. A bent-fitting edit is explicitly refused; this is not proof of general MEP coverage.

This snapshot is not a production readiness certification or a claim that every customer model is supported.

START WITH ONE USEFUL WORKFLOW

A scoped pilot. Concrete acceptance.

Proposed pilot: $500 for a defined IFC editing workflow, with scope and success criteria agreed before payment.

Define

Choose representative models and the edits your product needs. Establish what a correct result looks like.

Integrate

Use asynchronous convert, check and compile jobs. Keep your own AI stack and review output in your target software.

Evaluate

Inspect before/after artifacts, diagnostics and verification reports. Record supported cases and limitations explicitly.

Tell us what you want to build ↗

Access is provisioned individually. Hosted fresh-model generation (new) is not released. No native RVT conversion is promised.