Overview
BlendSmith is a model-independent production control loop for Blender agents. It does not replace the model, Blender, MCP, bpy, or GUI automation, but provides production structure by deciding whether real-world knowledge is needed, turning researched facts into practice rules, decomposing the job, exposing method-relevant operations, choosing dedicated Blender methods before scratch work, tracking dependencies, inspecting rendered and live-GUI evidence, classifying what went wrong, and returning to the right upstream decision before continuing. The core idea is that a visible defect does not tell you where the mistake was made, so the right response may be a local edit, a different Blender method, a Production Graph change, an upstream contract revision, or a return to the domain knowledge that produced the requirement. BlendSmith forces that distinction before the agent is allowed to keep patching. It is not a crutch for weak models; capable models already make strong 3D assets, and BlendSmith is the control layer for keeping a capable model on a coherent production path across a long run. The production loop includes a Domain Research Gate, Method Selection, Change Impact Gate, and Exploratory Live GUI Review, and it ends deliberately at AI_ACCEPTED != HUMAN_ACCEPTED, where the agent proposes actions, BlendSmith Core decides which transitions are valid, and the owner decides whether the exact reviewed artifact is accepted.
Pricing
Free
Detailed plans have not been confirmed in our catalog. Check the official website for current limits and billing terms.
Visit WebsitePrices and limits may change. Confirm the currency, billing period, seat minimum and usage caps on the official website.
Use Cases
- Teams use BlendSmith to keep an AI agent on a coherent production path across a long run.
- Teams use BlendSmith to decide whether domain research is needed before planning.
- Teams use BlendSmith to classify failures and return to the right upstream decision.
- Teams use BlendSmith to inspect rendered and live-GUI evidence for issues fixed renders miss.
- Teams use BlendSmith to enforce method selection before scratch construction.
- Teams use BlendSmith to prevent patch stacking and review the whole production context.
- Teams use BlendSmith to ensure approval names the exact reviewed bytes.
Features
AI assistant
Natural language interface
Workflow automation
Reviews
No reviews yet. Be the first to share your experience!