AXLEKEYSBETAAxle Keys is not only a website. Studio projects are accessible through controlled tools — so AI agents, development environments, and external workflows can read model state, create reversible drafts, validate changes, and prepare fabrication outputs.
Both connect to the same underlying Systems and project logic — designed for different workflows.
Use MCP when an AI assistant, coding tool, or autonomous workflow needs to interact with a Studio project step by step. MCP is the primary access layer — built around the reversible draft–validate–promote pattern.
Use the REST API when a website, configurator, database, or business system needs to call Axle Keys programmatically. The API is planned and launches alongside the first mature Systems.
Agents working with physical models need a safety pattern. Every meaningful change is staged, validated, and promoted — not written directly to the live project.
MCP tools are organized into rooms so the toolset stays understandable as it grows. Each room covers a distinct part of the agent workflow.
Orient the agent — what project is active, what workspace, what state the session is in.
Read and push model code, inspect screenshots, create projects and models.
Stage, validate, promote, and roll back changes safely.
Adjust dimensions and options without rewriting model code.
Check build status, geometry correctness, and model warnings.
Upload, list, and assign roles to reference files and drawings.
Create and track longer operations — exports, analysis, batch runs.
Download fabrication outputs from completed export jobs via signed URL.
Load System rules, skill packs, and modeling references.
Designed for developers and AI agents who need to work with physical models programmatically.
An agent reads the active model, creates a draft with a focused change, validates it, and promotes only when the model is clean. The live project is never directly overwritten.
Instead of rewriting model code, the agent updates exposed parameters and checks the result. Often safer, faster, and more reliable than code generation for small changes.
Pass customer inputs to the REST API, receive configured assemblies and cut lists, and fulfil orders directly from the output — no Studio tab required.
Connect Axle Keys to a local development environment, desktop app, automation script, or external agent. Axle Keys becomes the CAD execution layer while the external tool coordinates.
The REST API launches alongside the first Systems. Below is the planned endpoint structure.
MCP and API access are in active development. If you're building an agent, integration, configurator, or automation workflow that should connect to Axle Keys, get in touch.