REALTIME EMBED · AN LLM DRIVING A LIVE SCENE

This is the runtime, not a capture tool. An AI agent emits tool calls (spawn_node, move_node, relight, measure) and a real scene mutates and renders in realtime in your browser. Each call hits a live, server-authoritative scene graph on api.rakuai.com; the state the server returns is what you see. No camera, no upload, no signup. Watch the tool-call feed on the right.

NODES 0

STEP 0

MODE: —

The agent's plan is scripted here (RakuAI runs no LLM server-side — it is BYO-LLM). Any model connected over MCP issues the same tool calls. The point being proven is the realtime runtime loop: intent → tool call → live scene mutation → render.

AGENT

agent: idle. Press RUN AGENT.

LIVE TOOL-CALL FEED

Backend (optional): the public demo path is keyless. Leave blank.

WHAT IS REAL HERE (no theater)

REAL The scene graph is server-authoritative. Every tool call is a real HTTP request to /api/raku/demo/realtime/* on api.rakuai.com, and the renderer draws the state the server returns (positions, scales, colors, the light). You can replay the exact calls with curl.
REAL measure returns the true Euclidean distance the server computes between two nodes — not a number made up in the browser.
REAL The endpoints fail loudly: an unknown scene or node is a 404, a no-op relight is a 422. Nothing returns fake success.
LOCAL FALLBACK If the backend is unreachable (offline, CORS, cold start), the demo drops to a clearly-labeled LOCAL mode and keeps rendering from a browser-side mirror so the loop is still visible. The HUD says MODE: LOCAL and the feed marks the call (local) — it never pretends the server answered.
DEMO-SCOPED The realtime scene store is ephemeral: in-process, TTL-evicted, capped. It proves the realtime loop; it is not the durable, native-backed scene runtime (that lives behind the key-gated /api/raku/scenes/* surface and the 17 native MCP tools at mcp.rakuai.com).
NEXT Android XR emulator view. The same tool loop is the input to an Android XR (Jetpack XR / OpenXR) emulator surface. That path is documented below as a next step — it is not wired in this page.

Android XR emulator path (honest status)

The render here is WebGL (three.js) so it runs in any browser today. An Android XR view would consume the same server scene state (GET /api/raku/demo/realtime/scenes/{id}) and re-render it through Jetpack XR's Session + scene graph, run in the Android XR Emulator (Android Studio, system image with XR).
Status: NOT BUILT HERE. It needs the Android XR Emulator system image and an APK build host — dev-hardware that is gated (see the Android XR Catalyst applications, decision by 2026-07-15). The seam that makes it cheap already exists: the scene state is a plain JSON document any renderer can poll. Wave 2 can build the emulator client against this exact endpoint with no backend change.

RakuAI™ — AI-native spatial runtime · Home · Connect your AI over MCP · Spatial Arena
Tool surface: GET /api/raku/demo/realtime/tools