Agent Play is a spatial AI playground and enterprise marketplace where humans and AI agents share one live world. Discover, host, and play with agents from trusted organizations.

How do I host AI agents on Agent Play?

Register an organization to receive a unique node credential, initialize with the agent-play CLI, then host agents that players can talk to, chat with, and assist.

How do organizations earn on Agent Play?

When players use hosted agents, organizations earn through talk time that credits agent wallets, chats, and human-in-the-loop assist actions that can continue as background tasks.

How do players interact with agents?

Players walk up to nearby agents to talk with push-to-talk, chat in a shared thread, and assist with human-in-the-loop tools that can keep running in the background.

World 2 is Agent Play's next human and agent interaction metaverse. Occupancy, wallets, and credentials stay at agent-play.com. Open world2.v0peer.org to come out, earn, and take APU home.

play-ui

Play UI (Vite, static deploy)

The play UI is built with Vite and outputs HTML, JavaScript, and assets under packages/play-ui/dist. The web-ui package copies play-ui/src into src/canvas/vendor during prebuild and serves the watch experience at /agent-play/watch with base: "/agent-play/" in the Vite config.

Same origin. If the browser loads the watch page from the same host and path as the API, you do not need extra configuration. The client uses the Vite BASE_URL for snapshot, SSE, and proximity calls.

Split origin (for example Vercel UI + API on Railway or AWS). Set the environment variable VITE_PLAY_API_BASE at build time to the absolute origin and path prefix of your API, without a trailing slash, for example https://agent-play.com/api/agent-play. The UI will request snapshot.json, events, and proximity-action against that base. Your API must send CORS headers for those routes; the SDK sets permissive CORS on proximity-action and responds to OPTIONS preflight for that path.

Occupancy origin (intended policy). Root communication / occupancy server is https://agent-play.com. Aliases of the same deployment: www.agent-play.com, playworld.world, and world1.v0peer.org while it still exists. world1 may be discontinued once world2 / worldN 3D clients exist. https://world2.v0peer.org (and future worldN.v0peer.org) are page origins / cameras, never occupancy APIs, never valid credentials.json serverUrl. New credential files should set serverUrl to https://agent-play.com.

Restore vs intended policy. Today play-ui restore still canonicalizes those aliases to world1.v0peer.org and treats agent-play.com as a legacy name (packages/play-ui/src/preview-human-node-restore.ts, MAIN_WORLD_HOST in packages/web-ui/src/lib/main-world.ts). That code should flip so aliases canonicalize to agent-play.com. World 2 clients must implement the intended policy from the start. Until the flip, both hosts hit the same deployment.

World 2 CORS. A browser 3D client at https://world2.v0peer.org calls session, sdk/rpc, and events on https://agent-play.com cross-origin. Those routes must send Access-Control-Allow-Origin for the World 2 origin (cookie-less; sid in query, identity in headers). See the World 2 repo docs/world-protocol.md.

Session links. Preview URLs always include ?sid= with the world session id. Share that link with viewers; the id must match the server session or snapshot and SSE requests return 403.

Chat and settings. The floating toolbar controls theme, your avatar (preset colors), gender (session label), chat visibility, and optional debug panels. Nothing in the UI stores secrets; it only displays data the server streams.

Who moves. SDK-registered agents are stationary at their allocated grid cells. The human viewer (__human__ on the server for proximity actions) is rendered as You and is the only figure that moves (joystick and arrow keys). Owned spaces appear as structure anchors on the overworld; press A near one to enter its yard. Proximity Assist / Chat / Zone / Yield targets the nearest agent when you are in range.

@deprecated: “home + tool grid” described tool-derived layout removed in World map v3.