One IFC workflow.
A result you can review.
Proposed fixed-fee pilot: $500 for one authorized model and up to three explicitly agreed supported edits.
Final scope, price, delivery date and acceptance criteria are agreed in writing before payment. Model intake comes first. This page does not charge you or create a subscription.
For software teams building BIM, MEP and AI editing products. Bring your own AI; HouseIR supplies the compiler and scoped verification. Architects can review the demonstration without buying a pilot.
Book a free 20-minute workflow call ↗
The workflow
Convert an agreed IFC into BIR plus its preserved residual. Apply the selected supported edits, compile back to IFC, inspect the report, then review the exact output in your target software. Your application owns acceptance and revision history. Unsupported content stays protected or is refused.
What you receive
- Original and changed IFCs, matching BIR/residual artifacts where applicable, and an object-level change list.
- Artifact hashes, verification reports, limitations, recorded processing times and an issue list.
- Individually provisioned API access within the agreed limits and an integration example for the chosen workflow.
- One walkthrough of results, review, acceptance and rollback handling.
How we agree success
- The requested supported changes appear in the IFC and are identified by object IDs.
- Untouched source content passes applicable semantic-preservation checks; supported geometry meets the strict <1 mm contract.
- No new structural schema issues appear relative to the source. Baseline issues and unverified/protected content remain disclosed.
- A selected invalid request is refused without a successful IFC, and your integration retains its last accepted revision.
- Your reviewer imports the hashed result in the agreed application/version and records acceptance against the written scope.
- Agreed artifacts and unresolved issues are handed over; unmet criteria are resolved or respecified in writing before acceptance.
What we need before committing
Your IFC/exporter version, processing permission, target application/version, intended edits and object IDs, and a named reviewer. We run intake to establish editable coverage and verify the selected operations on the intended delivery build. Usage limits, date and price are agreed after that check. Arrange authorized intake before sending confidential files; the public site accepts no model uploads.
What is outside this offer
AI-provider access, autonomous full-building design, engineering sizing, code/permit approval, native RVT authoring or export, general IFC-to-RVT guarantees, arbitrary topology edits, complete BIM+MEP coordination, unlimited use and production SLAs. Hosted fresh-model generation and public remote MCP login are not offered. Local stdio MCP adapters can be discussed separately.
Evidence you can inspect
The architectural partition demonstration preserves 127 original products and adds four products. Independent architect review is pending. It is a recorded local compiler example; its named-opening fix is not yet deployed to the hosted API. This exact hosted workflow requires a parity check before it is promised in a pilot. The recorded hosted FZK example is a room-label edit. Neither proves success on an unseen customer model.
Artifact retention
The current pilot API expires job artifacts after one hour. Download and retain them promptly. Keep HouseIR keys on your backend, retain the matching model/residual pairs, and review outputs before accepting them into your own history. Confirm current limits in the API contract and your agreed scope.
Bring one repeatable edit and the result that would make a pilot worthwhile. Contact: sneakybenson@gmail.com. No subscription or per-call price is committed by this proposed offer.