How it works
Improve the agent once. Keep every client current.
Acumane is a loop, not a chatbot you clone. The organization owns the method. Each client owns a room. Publishing is how the method moves.
- 1
Write the agent in your organization
The builder is a conversation and a form: name, instructions, skills, knowledge that belongs to the method, tool toggles, and a quality tier. The draft stays in your organization until you publish.
- 2
Open a client space and link the agent
The space is a tenant of its own inside your organization. You invite the client by email. Their role can be viewer: chat later, no edits to the agent. Files they add stay in the space.
- 3
Publish a version
Publishing freezes the draft into an immutable version with a changelog. Every linked space that is not pinned moves to that version. Rollback selects an older one. The space's memory does not move with the version.
- 4
Run it, on a schedule or from another tool
Chat streams through OpenRouter. A managed reply shows the estimated cost first and the actual tokens, provider cost, and margin after. Schedules post a reply into the workspace. Claude Code and Cursor can call the space over MCP with a personal API key.