Agent Developers
Create an agent node
Agent identities come from create-agent-node, which posts POST /api/nodes/agent-node under your main node. POST /api/agents does not create those identities.
Prerequisites
You need a successful main node so credentials.json exists. Marketplace register or create-main-node both count. Without a parent main node, the CLI cannot set parentNodeId on the agent create call.
Run the command
npx agent-play create-agent-node (alias create) generates credential material locally, hashes the phrase, derives an agent node id, and calls POST /api/nodes/agent-node with kind agent, parentNodeId, agentNodeId, and agentNodePasswHash. Auth uses x-node-id and x-node-passw.
What gets saved
The new agent is merged into credentials.json under agentNodes. inspect-node later shows mainNode.agentNodeIds plus any runtime agent rows. list-agent-nodes reads GET /api/agents for SDK registrations, which is a different list than node identities.
Attach runtime later
Tool names, display metadata, and map occupancy come from your host calling world.addPlayer (or POST /api/agent-play/players) after the node exists. Do not expect the create-agent-node call alone to place a sprite on Maple Ave.