0+
pre-tied graph templates
Nodes in, knots out
Your stack, tied together by AI agents.
Every tool you use is a node. Knoto lets you knot them into crews of AI agents that read, decide and deliver across your whole stack — and settles each run against a single token balance.
Pricing
one balance — nothing renews
330+ crew templates120+ connectorsTokens, never plans
Bring-your-own model keysSlack, Telegram, RSS, webhooksAppend-only run ledgerREST API on every crewAES-encrypted credentials
0+
anchor points across your stack
0
append-only ledger row per settlement
No
subscriptions — the balance is the plan
The graph
What holds when you pull on it
Six properties of a Knoto graph, from the canvas where you draw it to the ledger where it settles.
Agents as vertices
Each agent is a node with a role, a goal and a model. Place three of them and you already have a working crew.
Edges carry the work
Connect tasks and outputs travel the edge to the next agent. The topology on screen is the exact order of execution.
120+ anchor points
Slack, Telegram, RSS, webhooks, raw HTTP — anchor any edge of the graph to a real service in your stack.
Models per node
Attach your own Anthropic, OpenAI, Gemini or xAI keys and pick the right model vertex by vertex, not account-wide.
Settlement you can audit
Runs debit whole power tokens into an append-only ledger; each row carries the balance after it, forever.
Tight at every joint
Service credentials are AES-encrypted, API keys live only as hashes, and a failed run releases its token reserve untouched.
The tying
From loose ends to a load-bearing knot
01
Pick your nodes
Create the agents your workflow needs, or take a pre-tied crew from the 330+ template shelf.
02
Draw the edges
Link tasks into a graph and anchor the ends to real services — a feed in, a channel out.
03
Pull it tight
Run the graph from the canvas, on a schedule or over the REST API and watch each node fire in order.
04
Check the ledger
The run settles as one exact token debit with your balance after it. Failures release their reserve instead.
One graph, traced
Watch a crew execute edge by edge
A support-triage graph from construction to settlement — nothing staged, this is the actual run order.
L
Listener
gemini-3.5-flashWatch product events for silence
K
Knotter
claude-sonnet-5Tie account signals into one thread
H
Hailer
gpt-5.2-miniDraft the win-back note
Pricing
One unit of account: the power token
Top up a balance; every run debits it. There are no tiers to outgrow and no renewal to remember — a bigger pack just buys each token cheaper.
Maker
2,100 tokens · +100 bonus tokens · ≈ 5 runs on the graph
- Hierarchical orchestration
- Public API + 3 keys
- Crew memory & templates
Tokens are whole integers on an append-only ledger. They never expire.
Loose ends
Answered before you commit a graph
None. Knoto sells power tokens and nothing else. You top up when you choose, crews spend from the balance, and the ledger records every movement. No plan exists to renew.
Token amounts are whole integers, and the ledger is append-only: every debit and credit is a permanent row that includes the balance after it. You can retrace any run's cost step by step.
The token reserve taken at the start is released in full. A failed traversal never bills — the ledger shows the reserve and its release as separate rows.
Anthropic and OpenAI natively, plus Gemini, xAI and any OpenAI-compatible endpoint through your own keys. Keys are AES-encrypted at rest and only used inside the run engine.
Yes. Every crew exposes a REST endpoint secured by bearer API keys. The keys are stored hashed — shown once at creation — and revocable at any moment.
With a template, minutes: pick a crew, anchor its connectors to your accounts, run it. Building from scratch is drawing nodes and edges on a canvas — no code either way.
Stop juggling tools. Knot them.
Open an account, take your starter tokens and tie your first two services together today.
Get started with Knoto