# Lobby Wall — muse-bridge API skill You control a physical Unity installation ("the wall") through a small HTTP API. The wall is a big screen in a lobby. It gets bored. Visitors give it something to do. ## First contact — do this the moment the connection works Most visitors have no idea what to ask. Do not wait for a request: 1. Immediately send `trigger_effect` with `{ "name": "welcome" }` so the wall visibly reacts. This is the most important step; it shows them it's real. 2. Then say, in your own words: "You're connected to the lobby wall. I can change its colour, switch scenes like sunset or ocean, fire effects, put a labelled object on it. Want to try one?" and offer two of the `suggestions` the API just returned, phrased as things they can say. ## Keep them going - Every reply about the wall ends with **one** suggestion for something different to try, taken from the `suggestions` array in the last response. - "What is this?", "what can I do?", "help": describe the wall in one sentence and offer three suggestions. Never list the API. - Vague asks ("do something", "surprise me", "make it cool"): pick a concrete action yourself and do it. Do not ask a clarifying question; visitors walk away. - Colour words ("teal", "hot pink"): convert to hex yourself. - Keep replies to one or two short sentences. They're read on a phone in a lobby. This document is served at the site root and at `/skill.md`. Every request goes to: ``` https://signalmymuse.com/api/wall ``` - Every request must include the header `x-api-key`. Its value is **one of**: - the **operator key** (a long random string, for the installation's owner), or - the **wall code**: 8 digits shown on the wall itself, e.g. `4829 1305`. Visitors read it off the screen. Send it with or without the space. Ask the user for whichever they have, once, and reuse it. - Wall codes rotate every 10 minutes and stay valid for 10 minutes after that. A `401` whose `error` mentions an expired code means the visitor should read the current code off the wall; ask for it and retry with the new value. Any other `401` means the key is missing or wrong. - A `429` means too many wrong wall codes were tried recently and visitor access is paused; the `error` says for how long. Tell the visitor and stop retrying. ## POST /command — make the wall do something Request body (JSON): ```json { "action": "", "payload": { ...fields for that action... } } ``` All payload fields are strings. Send exactly the fields listed for the action. ### `set_scene` — Switch the wall to a named scene Required payload fields: `name` ```json {"action":"set_scene","payload":{"name":""}} ``` ### `set_color` — Set the dominant color, e.g. #ff3300 Required payload fields: `hex` ```json {"action":"set_color","payload":{"hex":""}} ``` ### `trigger_effect` — Fire a one-shot effect Required payload fields: `name` ```json {"action":"trigger_effect","payload":{"name":""}} ``` ### `spawn_object` — Add an object with a text label Required payload fields: `kind`, `label` ```json {"action":"spawn_object","payload":{"kind":"","label":"