SchemAgentic
AI
AI appears in four places in SchemAgentic, and they are not the same thing wearing four hats. This page is what each one is, what it costs, and what leaves your machine.
Where the AI is
| Where | What it does | Runs |
|---|---|---|
| The map chat | Builds the schema: nodes, content, agents, services and connections, from a description. | When you ask |
| The agent chat | A conversation with one agent about its own work. It can propose changes to itself; you press. | When you ask |
| Agents | Standing instructions carried out on a schedule, on our servers, with the document closed. | On their own |
| Drafting a service | Describe an API and a service definition is drafted for you to check before it is saved. | When you ask |
There is a fifth, in the other direction: the MCP server lets an external AI agent — Claude Code, Claude Desktop — read and add to your maps.
Choosing a model
The chat has a model picker. The default suits almost everything; a heavier model is worth it for a large restructure or a subtle question, and costs more of your allowance per turn.
Agents have their own model setting, separate from the chat's. An agent that runs hourly on a cheap check should not be on the most expensive model.
What it costs
AI is measured in units — tokens weighted by what the model costs, so one unit means the same amount of money whichever model produced it. Your plan includes a monthly allowance; the editor shows what this schema has used and the file list shows the account total.
In a shared schema, the owner pays. Every turn, every agent run, every service call is billed to whoever owns the schema — not to whoever triggered it.
But doing those things needs a subscription of your own as well, even in somebody else's schema: running an agent, talking to one, calling a service. Reading a schema and everything its agents have written needs nothing at all.
An agent can also be given its own monthly budget, under the account's. That is what stops one misconfigured agent spending an entire allowance before anybody notices. Talking to an agent does not draw on that budget — it is for its runs, and a conversation should not be able to stop it working.
Your data
The AI is Anthropic's Claude, reached through our own server rather than from the app. The app never talks to Anthropic directly, and no API key of yours is involved.
What is sent, and only when you ask for it:
- The map chat: an outline of the schema — each node's id and title — plus your message and anything you attached.
- The agent chat: that agent's instructions, schedule, settings, budget and its recent runs, plus your message.
- An agent run: its instructions, its node's text, and the results of the service calls it makes.
What is never sent:
- Service credentials. Keys live in Secret Manager and are attached to a request on the server, after the model has decided what to call. An op carrying one is dropped rather than forwarded — see the chat page.
- Other people's schemas, or anything outside the one you have open.
What an agent reads is not trusted. When an agent tells you what it found, that text came from Stripe, Slack or whatever else it reached — written by other people. It reaches the model fenced and marked as data, and no reply can change a running agent on its own: it proposes, and you press. Why that matters.
Conversations are kept on your device and in your schema so you can come back to them. Deleting a schema deletes its chats with it.
When you run out
- At 80% of the monthly allowance the account carries a warning.
- At 100%, new agent runs and new turns are refused with a message saying so. A run already in progress finishes its current step rather than stopping halfway through something.
- The allowance returns on the 1st.
Agents on a schema whose owner is no longer subscribed are paused, never deleted, and start again by themselves when the subscription does.
Not yet
Two things you may expect and will not find:
- Generating a whole schema from a description. Building a mind map from a topic is one problem; building a schema — nodes, services, agents, connections, credentials — is another, and doing it badly would produce something that looks finished and is wired wrong. The chat builds a schema piece by piece instead, which you can follow.
- Using your own Anthropic API key. Not available in this app.