Build on Kamai.
Every primitive Kamai sees is available through the API. Push a drawing in, get structured data back - REST API today, MCP server for your agents next. Build the next layer of AEC software on top.
Your first Takeoff API call.
Grab a key from the Kamai Console, upload a sheet set to POST /v1/blueprints/upload, then poll the project and fetch the GeoJSON result. Pick your language, copy, run.
# 1. Upload a sheet set (multipart). Returns { job_id, project_id }.
curl -X POST https://api.kamai.io/v1/blueprints/upload \
-H "Authorization: Bearer $KAMAI_API_KEY" \
-F "[email protected]"
# 2. Poll the project until the job leaves PENDING / RUNNING.
curl https://api.kamai.io/v1/projects/$PROJECT_ID \
-H "Authorization: Bearer $KAMAI_API_KEY"
# 3. Fetch the result once the job is SUCCEEDED.
curl https://api.kamai.io/v1/blueprints/$BLUEPRINT_ID \
-H "Authorization: Bearer $KAMAI_API_KEY"Everything a real platform needs.
API keys
Authenticated REST API. Create and manage keys self-serve in the Kamai Console.
Webhooks
Subscribe to events like takeoff.completed as runs finish. Coming soon.
Embeddable takeoff
Drop the takeoff widget into your own product with @kamai/iframe-bridge.
MCP server
Kamai as MCP tools in Claude Desktop, Claude Code, and Cursor. Coming soon.
Every URL you need, in one place.
The console, packages, and live demos - click through or copy the exact URL.
The PostMessage SDK for embedding the takeoff widget.
npmjs.com/@kamai/iframe-bridgeA working host-page integration you can fork and poke at.
codesandbox.io/iframe-bridge-demoNew to the category? Start with the guides: the construction takeoff API, explained and extracting quantities from blueprints.