LIVE GAME STATErelay 02
runtime memory → semantic state → agent

AI can read the world underneath.

loot.moe gives an AI companion structured live game state instead of asking it to guess from pixels. Play on one screen. Ask about the same game on another.

The bridge is now real.

cross-device loop

Game here. Companion there.

The browser emulator samples verified Soma Bringer RAM semantics and publishes a session to loot.moe. Any authorized companion can read the same session through the read-only API.

Soma Bringer / browser ↓ semantic RAM adapter v0.7 ↓ loot.moe session relay ↓ Companion API ↓ “What did I just find?”
live coverage

Meaning, not pixels

HP / SPgoldinventoryequipmentCP / APabilities
privacy boundary

Your ROM stays local

The deployment contains the emulator runtime and semantic adapter, but no Soma Bringer ROM or save. You choose a local ROM file in the browser.

agent surface

Read-only OpenAPI

The public OpenAPI describes only companion reads. Runtime publishing uses a separate publish credential.

next semantic

Identification lifecycle

The next useful game-state transition is unidentified → identified while the object remains the same loot.

Companion-facing routes.

READ SURFACE/api/v2

These routes take a session query parameter and the read bearer token. The browser bridge publishes to the matching session with a separate publish token.

GET /summarycompact live contextAI READY
GET /latest-lootwhat just dropped / entered inventoryAI READY
GET /buildstats + points + abilities + equipmentAI READY
GET /inventorydecoded on-hand itemsAI READY
demo stateSoma Bringer
loading…