PDF, Revit, and Excel under a single agent-first dispatcher. Self-installing, self-describing, no accounts, no telemetry, no network calls after install.
iwr -useb https://bimcli.com/install.ps1 | iex
Per-user. No admin. Idempotent — re-run to upgrade.
You have access to bim-cli, a Windows CLI for AEC formats (PDF, Revit). It is fully offline — no network, no accounts.
Run `bim describe --json` once to see all drivers, verbs, and arg schemas. Run `bim doctor --json` to verify the environment; each failed check has a `fix` field with the exact command to run.
Then call commands as `bim <format> <verb> [args]`. All output is JSON on stdout; everything else is on stderr. Errors return `{"ok":false,"error":{"kind","message","hint","retriable"}}`. Exit codes: 0 ok, 1 generic, 2 usage, 3 not-found, 4 permission, 5 conflict.
bim-cli is a single Windows command, bim, that wraps existing AEC tooling (the
Revit add-in via revit-cli, PDF analysis via pdf-cli) under one self-describing handshake an
AI agent can install and use in two commands. Excel ships next.
It exists because the AEC stack is broken in ways agents can finally fix — Revit's PDF export pain, the headless-automation gap Autodesk explicitly punts to paid cloud services, the bulk-edit tax that costs $895/seat for what is effectively parameter editing, and the Bluebeam-alternative search that has gone unanswered for years. None of those need a new application — they need primitives an agent can chain.
Designed for AI agents first; usable by humans. Per-user install, no admin, no telemetry.
bim describe --json — every driver, verb, and arg in one documentbim doctor --json — env health (Revit version, add-in, ports)bim pdf info <file> — PDF metadata, page count, XMPbim revit status — running Revit + add-in statebim info <file> — auto-detect format and route