SPATIAL ARENA

An AI agent plays a game inside a rendered 3D scene by calling the RakuAI Spatial API — the same 17 native MCP tools an LLM uses to drive the runtime (add_scene_node, set_node_transform, get_scene_state, remove_scene_node, capture_scene …). Every move below is a real tool call against a scene graph; watch the live tool-call feed on the right.

SCORE 0

TARGETS 0

TIME 60s

DRIVER: —

ORB HUNTER

Targets are spawned as nodes in the scene graph. Hit them by driving the reticle through the Spatial API. Let the agent play, or take the controls yourself.

You play: move the mouse / drag to aim the reticle, click / tap to fire — each action emits the same set_node_transform / remove_scene_node calls the agent makes. Drag empty space to orbit the camera.

⚙ LIVE RUNTIME PROBE

The game above runs the Spatial-API contract in your browser (local mode — always works, no login). To prove the same calls reach the production runtime, paste an API key and run a real round-trip against api.rakuai.com.

X-Raku-API-Key (optional)

Probe sequence: POST /api/raku/scenes → POST …/nodes → GET …/nodes → DELETE …/nodes/{id}. Real HTTP status + node IDs are shown in the feed. No key? It honestly reports that the call was not authorized.

📡 SPATIAL API CALL FEED

HONEST STATUS — what's real here vs. what's next

An investor-grade demo earns trust by being precise about its seams. Here is exactly what this page does.

REALRunning today

The 17-tool Spatial API contract is faithful to the production tools.v1.json — identical tool names, argument shapes, and return payloads (node ids, transforms, physics, capture_scene SVG).
A real 3D scene is rendered (three.js; a Gaussian-splat backdrop via Spark when a capture URL is supplied with ?splat=…), and the renderer draws whatever the scene graph contains — drive the API, objects appear/move/vanish.
An agent loop plays the game by calling the tools (get_scene_state → choose target → set_node_transform → fire → remove_scene_node), with hit detection and scoring — visible in the feed.
The Live Runtime Probe sends the same calls to the production REST scene graph (/api/raku/scenes/*) and shows the real HTTP responses — no faking: a missing/!invalid key reports the real error.
window.RakuSpatial and window.RakuArena are exposed, so a real LLM agent (e.g. Claude in the browser) can drive this scene directly from the console.

DEMO SCOPEHonest simplifications

Gameplay runs in local mode by default: the scene graph lives in the page so the booth demo works with zero credentials and zero latency. It mirrors the server contract; it is not the server's in-process graph.
The autoplayer is a scripted agent issuing the real tool sequence — it demonstrates the control loop deterministically rather than calling out to an LLM for each shot.

NEXTTo make the rendered scene fully agent-driven in production

Wire the capture viewer to read the runtime scene graph live — today it renders one splat and has no node bridge. Needs a transform-carrying get_scene_state over REST/WS.
The scene graph is currently ephemeral in-process state; a shared/persisted scene (Redis or engine-backed) lets the agent's session and the viewer's session see the same world.
Production scene mutations require the developer tier — fine for a keyed demo, to be formalized for public play.