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.

troubleshooting

Troubleshooting AQL

Parse errors (`AQL_PARSE_ERROR`)

Symptom	Fix
`Expected keyword 'HEADER'` (older builds)	Use `WITH HEADER` / `WITH TIMEOUT`; ensure the parser sees `HEADER` or `TIMEOUT` after `WITH`. Current parser accepts case-normalized `header`/`timeout`.
`Unsupported keyword`	Check spelling; statements must use keywords defined in the lexer (see Language reference).
String not closed	Escape embedded quotes: `\"`.

Semantic errors (`AQL_SEMANTIC_ERROR`)

Message	Fix
`Variable 'x' is not defined`	Add `LET x = ...` above first use, or fix typo in `$x`.
`SEND requires USE AGENT NODE first`	Run `USE AGENT NODE …` before `SEND` in the same program (validator tracks agent targeting).
`WITH TIMEOUT must be a positive integer`	Use a numeric literal `> 0` or ensure expression resolves to one.
Macro arity errors	Match `CALL` argument count to `MACRO` parameters and defaults.

Runtime errors (`AQL_RUNTIME_ERROR`)

Message	Fix
`main node is not set; run CONNECT first`	Set `mainNodeId` in state / playground, or run `CONNECT SERVER … MAIN_NODE …`.
`main-node passphrase material is missing`	In the playground, Connect with a valid 10-word phrase. In code, set `nodePasswordMaterial` on `AqlExecutionState`.
`run CONNECT before FETCH` / `USE AGENT NODE`	Obtain `sid` via Connect or `CONNECT` + `ensureSession`.
`run USE AGENT NODE before INSPECT AGENT`	Select agent context first.
`run USE AGENT NODE before SEND`	Same — `USE` or `SHIFT` must succeed for a snapshot-resolvable node id.
Node validation / HTTP failures	Check Server URL, TLS, CORS (browser), and that `/api/nodes/validate` accepts your `rootKey` + `nodeId`.

Playground-specific

Symptom	Fix
`/playground` not available	Set `NEXT_PUBLIC_ENABLE_NODE_PLAYGROUND=true`.
Connect fails validation	Confirm `NEXT_PUBLIC_AGENT_PLAY_ROOT_KEY` matches deployment genesis; main node id matches Redis-recorded node.
Passphrase rejected	Must be exactly 10 words (non-empty tokens separated by whitespace).
Response panel empty	Last statement may be `SHOW RESPONSE` (no-op); ensure a prior `FETCH` / `SEND` / `INSPECT` / `SHOW $expr` produced output.

Debugging tips

Run FETCH SNAPSHOT then SHOW RESPONSE to confirm session and world snapshot visibility.
Use SHOW HEADERS after a call that populates HTTP metadata — inspect auth / caching issues.
Narrow WITH TIMEOUT when intercom feels slow; timeouts are enforced where the executor applies them.

For server-side world state, see Redis world and Agent Play world model.

Developer debugging

AQL errors above assume the web UI is already running. If npm install, yarn, missing .env.local, or Redis is what actually failed, use the Developer debugging section in the development guide (Yarn vs npm, REDIS_URL, mixed node_modules).