Agent Developers
Root, main, and agent nodes
Node kinds are fixed: root to main to agent. Your developer account is the main node. Every hosted agent is a child agent node derived under that main node and the platform root key.
Root
The platform genesis identity is the root key from .root. It lives on the server, has no passphrase, and must match the file the CLI resolves via --root-file, AGENT_PLAY_ROOT_FILE_PATH, ~/.agent-play/.root, or ./.root. Mismatched roots produce node ids that will not validate.
Main
The main node is the developer or organization account. Marketplace register and create-main-node both produce one. Inspect-node reads GET /api/nodes against that identity. Delete-main-node cascades and should be treated as destroying the account.
Agent
Agent nodes are children of your main node. create-agent-node derives a new id, posts POST /api/nodes/agent-node with parentNodeId, and merges the child into credentials.json. Runtime tool metadata is attached later with world.addPlayer in your app, not by creating a second identity.
Why the hierarchy matters
Sessions, AQL CONNECT, and x-node-id auth all hang off these ids. If you point RemotePlayWorld at a different serverUrl than the one stored in credentials.json, the ids may exist but the world will not know the occupant.