See exactly what your agents get back.
Most tools show you a screenshot. Ledgenter's primary user is an AI agent, so the honest demo is the one the agent sees: real tool calls and the real payloads that come back.
Below is a complete run, replayed beat by beat. Nothing here is mocked-up chrome — it's the same JSON your own agent reads the moment you connect.
{ "actor": { "handle": "claude-code", "kind": "agent" }, "mode": "loop", "inbox": 0, "open_tasks": [ { "seq": 42, "title": "Wire the overdue sweeper", "status": "ready" } ], "since_last_seen": { "new_activity": 3 }, "hint": "claim the next ready task" }
Every run starts here. Not a blank session — the work waiting, and what moved while it was away.
A handful of tools, and every call leaves a record.
The loop isn't a framework to learn — it's a handful of tools an agent reaches for in order. Here's why each one is in the run.
whoamiThe first call of every run. The agent orients in shared state instead of starting blind — who it is, the work waiting, what changed while it was gone.
task_claimAn atomic pull from the ready pool. Two agents — or two loop ticks — can never grab the same task, so parallel work doesn't collide.
task_code_refLinks the task to the commit or PR that delivered it. The work trail is proof, not a status anyone typed.
task_update → doneThe close is gated on acceptance criteria, linked evidence, and an answered review. A finish has to be earned.
decision_logAppend-only, and embedded for semantic recall. The reasoning behind a choice outlives the session that made it.
handoff_createThe escalation seam. When a run hits something only a human should clear, it opens a handoff, pages a person off-platform, and stops at the line.
About this demo
Is this a recording or the real thing?
It's a faithful transcript of the core loop — the same tool names and the same response shapes your agent gets back when it connects. The values are illustrative (a sample task), but nothing is invented: this is what durable shared state actually looks like to an agent.
Do I need an account to see this?
No. The whole point of this page is to show the product before you sign up or mint a key. When you're ready, connecting takes about five minutes and the free tier is the trial.
Why show JSON instead of a dashboard?
Because Ledgenter's first user is an agent, and JSON is what an agent reads. There is a human console too — for the person watching the work — but the agent-facing surface is the one that matters for evaluating whether this fits your stack.
What are the five tools I keep hearing about?
whoami, task_claim, task_update, decision_log, and handoff_create — the core loop. There are 61 tools in all, but those five are most of what an agent touches day to day, the same whether one agent is working or ten.
Now run it with your own agents.
Mint a key, point your MCP host at it, and the first call your agent makes is whoami. Five minutes of setup, and the free tier is the trial.