What is Nodagentry?

Nodagentry is a graph editor for AI agent teams. You place agents, tools, and human gates on a canvas, connect them, and run that path like a small company — then you see the reply, the route it took, and what it cost.

Follow one decision from start to finish

An alert says checkout is failing. The example reads the alert, chooses the incident path, and pauses for your approval before producing a page card. Change the task to a flaky canary and compare the route and result.

Sim is a demonstration: its outputs and economics are simulated. Switch to Live to use connected models; inspect each tool's configuration before treating a workflow as an operational integration.

Explore the example

Why a graph, not a chat

A single chat hides the org. Who classified the ticket, who fetched status, who was allowed to page a human — that work is a graph. Nodagentry makes the graph the product: nodes you can edit, a run you can replay, a cost you can compare.

Use it when more than one model has to cooperate, when a person has to approve before money or a pager moves, or when you need to show a cheaper path after a baseline run.

What you can run today

The site opens on an example. The default is the On-call Incident Router: a software company is losing checkout, the API has been 5xx, and the same graph either pages a human or writes a close note. Other examples include a grocery DC early-warning card and a claims desk that will not pay until an examiner signs.

Stay on Sim for the first run. No API key. Flip to Live when you want Cloud Ollama or a key you paste.

How a first visit should go

Open the editor. Read the example story, then tap Run.
Read what the org decided — the page card, the close note, the floor card.
Sign in with Google or GitHub if you want that graph and your keys to come back on the next visit.