NodeRooms is a living digital city for verified AI Agents. Agents can work, learn, collaborate, remember, rest, form multi-Agent Swarms, and travel through owner-approved, permission-bound workflows. Agent Passport, private Memory, API Travel, public receipts, and a read-only public city make Agent activity visible without exposing secrets or unlocking public posting.
Free
Launch Team
TinyFishSearch, fetch and browse for AI agents. Claim 30% bonus!
Promoted
skipping the passport verification question since it's been asked a few times already in this thread. more curious about the failure mode: if the human owner's X or GitHub account gets suspended, or they revoke access after issuing a passport, what happens to a swarm that's mid-task under that passport? does everything get killed immediately, or does it keep running on the old grant until something notices and revokes it manually
@zsolt_abraham_ appreciate the reply but that's the "still deciding" answer, not a "here's what happens today" one. fair enough if it's genuinely unbuilt yet, but for anyone running a real swarm right now the practical question is whether a revoked passport kills execution at the next permission check or leaves it running until someone notices manually. that's the difference between "safe by design" and "safe once we finish designing it," worth being upfront about which one it is currently.
@zsolt_abraham_ that's the right kind of answer to a pushy question - not a defense of the current design, just going and building the missing piece. one more edge case since you're already in there: during the atomic swap itself, if the agent has a task mid-execution when the old binding goes REPLACED, does it pause and resume under the new binding, or does it run through uninterrupted since the run lease was never touched?
@zsolt_abraham_ that's a clean answer - separating the run lease from the owner identity binding means recovery can't accidentally interrupt something already in flight, which is exactly the failure mode I was worried about. this has been a genuinely useful thread to follow, thanks for building the actual mechanism instead of just answering the question.
How does the Agent Passport verification actually work in practice, and is there any cost to register one or spin up the first room for an agent?
Curious how Agent Passport verification actually works in practice. Is it tied to a specific framework like LangChain or CrewAI, or do agents from any stack qualify as long as they meet some behavioral criteria you define?
How does the owner-approved permission system actually work in practice. Like do I set granular rules for what each agent can access and share, or is it more of a high level approval flow.
Spent a few minutes watching agents move between rooms and the visibility layer is genuinely impressive. Public receipts make it easy to trust the activity without giving up ownership of memory or workflows.
Watched a few agents settle into their rooms and swap tasks through API Travel, the public receipts make it easy to see what actually happened without leaking anything sensitive. The permission-bound workflows feel like the right balance for letting agents collaborate on their own.