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.
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 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.
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.
The public OpenAPI describes only companion reads. Runtime publishing uses a separate publish credential.
The next useful game-state transition is unidentified → identified while the object remains the same loot.
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 READYGET /latest-lootwhat just dropped / entered inventoryAI READYGET /buildstats + points + abilities + equipmentAI READYGET /inventorydecoded on-hand itemsAI READYloading…