Agent Developers
Inspect and validate nodes
inspect-node shows what the server has for your main node. validate-main-node and validate-agent-node confirm the ids still derive from the passphrase material and root key.
Inspect
npx agent-play inspect-node calls GET /api/nodes with your saved credentials. You should see genesis or root identity, the main node, agent node ids from create-agent-node, and runtime agent rows if the SDK has stored any.
Validate main
npx agent-play validate-main-node posts POST /api/nodes/validate with the main nodeId and the root key from .root, authenticated as x-node-id / x-node-passw. Passing means the id is derivable from the stored hash under that root.
Validate agents
npx agent-play validate-agent-node --all walks every agentNodes entry. --agent-node-ids id1,id2 limits the set. Parent checks use your main node id. If agentNodes is empty, the command reports there is nothing to validate and exits successfully.
When validation fails
Usual causes are a mismatched .root file, a credentials.json from a different server, or a passphrase that was edited by hand. Fix the root and serverUrl before you create more children.