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.

docker-compose

Docker Compose (main server + agents)

The main Agent Play server (@agent-play/web-ui: Next.js + WebSocket + Redis) and the built-in LangChain agents (@agent-play/agents: Express health endpoint + SDK registration) run as separate containers. Redis stays with the web UI; the agents process talks to the main server only over HTTP (RemotePlayWorld), so you can scale or relocate the agents tier without colocating it with Redis.

Images

Image	Dockerfile	Role
Web UI	`k8s/Dockerfile.web-ui`	Main server on port 8888 (override with `WEB_UI_PORT`).
Agents	`k8s/Dockerfile.agents`	Sidecar HTTP on 3100 (`/health`); registers built-ins using `RemotePlayWorld` and a mounted `credentials.json`.

Building the agents image requires a .root file in the repository root (same as local SDK builds); see World model / player chain.

Credentials for the agents container (required)

The CLI writes ~/.agent-play/credentials.json on the host. The SDK’s default path (when AGENT_PLAY_CREDENTIALS_PATH is unset) is join(homedir(), ".agent-play", "credentials.json").

The agents image sets HOME=/home/agentplay and creates /home/agentplay/.agent-play/. Compose bind-mounts your copy of the file to the same logical path inside the container so resolveAgentPlayCredentialsPath() is unchanged—no env override:

Host path (override with `AGENT_PLAY_CREDENTIALS_HOST_FILE`)	Path inside container (same as `~/.agent-play/credentials.json` for user `agentplay`)
`./agent-play-credentials.json`	`/home/agentplay/.agent-play/credentials.json`

Before docker compose up:

Copy your CLI file next to docker-compose.yml: cp ~/.agent-play/credentials.json ./agent-play-credentials.json.
Set AGENT_PLAY_WEB_UI_URL (or rely on the default in docker-compose.yml) so the agents container reaches the web UI by Compose DNS, e.g. http://web-ui:8888. That value is passed as baseUrl to RemotePlayWorld and overrides serverUrl from credentials.json for HTTP. You can still edit serverUrl in the file for consistency; auth fields are unchanged.
- Full stack: default is http://web-ui:8888 (override with AGENT_PLAY_WEB_UI_URL if your service name or port differs).
- Standalone agents: set AGENT_PLAY_WEB_UI_URL to your deployed origin, e.g. https://play.example.com (required by docker-compose.agents.yml).

The /health endpoint and startup log prefer AGENT_PLAY_WEB_UI_URL when set; otherwise they use serverUrl from the mounted file, then http://127.0.0.1:3000 if the file is missing.

Full stack (one host)

From the repository root:

cp ~/.agent-play/credentials.json ./agent-play-credentials.json
# Optional: AGENT_PLAY_WEB_UI_URL=http://web-ui:8888 (default in docker-compose.yml)
docker compose up --build

Web UI: http://localhost:8888 (or WEB_UI_PORT).
Agents health: http://localhost:3100/health (target prefers AGENT_PLAY_WEB_UI_URL, then serverUrl from credentials).

Other optional variables in a .env file next to docker-compose.yml:

Variable	Purpose
`AGENT_PLAY_WEB_UI_URL`	Base URL for `RemotePlayWorld` and health `target` inside the stack (default `http://web-ui:8888`)
`OPENAI_API_KEY`	Built-in LangChain agents
`AGENT_PLAY_API_KEY`	If the repository requires an API key for registration
`AGENT_PLAY_MAIN_NODE_ID`	Optional override for `connect({ mainNodeId })`
`PLAY_PREVIEW_BASE_URL`	Public origin for preview URLs on the web UI (defaults to `http://127.0.0.1:8888`)

Agents only (standalone server)

cp ~/.agent-play/credentials.json ./agent-play-credentials.json
export AGENT_PLAY_WEB_UI_URL=https://your-main-server.example
docker compose -f docker-compose.agents.yml up --build

AGENT_PLAY_WEB_UI_URL must be set to the origin the container can reach (Compose validates this).

Listen address (containers)

The agents Express server binds AGENT_PLAY_BUILTINS_HOST (default 127.0.0.1 locally; the image sets 0.0.0.0 so /health is reachable from outside the container).

Build commands (without Compose)

docker build -f k8s/Dockerfile.web-ui -t agent-play-web-ui .
docker build -f k8s/Dockerfile.agents -t agent-play-agents .