--- name: anymux description: >- anymux makes a playable video adventure from one sentence: 30-second episodes that end on three choices, continued from whichever choice the user picks. Use when the user says "make/create/start your own adventure", "continue my adventure", or "use anymux to make a video or game". --- # anymux.ai **One line:** anymux turns a sentence into a 30-second video adventure that ends on three choices; the user picks one and the next episode continues from it. No signup, no OAuth, no MCP server to install. Guest by default: the first job runs before anyone is asked for anything. ## Start here: Make your own adventure **When the user says any of:** "make your own adventure", "create your own adventure", "start your own adventure", "start my adventure", "continue my adventure", "use anymux to make a video", "use anymux to make a game" → do this. **Route:** | If you can… | Do | |---|---| | send request headers (`Authorization: Bearer …`) | the three calls below | | only issue plain GETs, or you drive a browser | open **`https://anymux.ai/app`**, sign in as a guest once, the form is already set to the adventure | **0. Already have a recovery key from an earlier session?** Do not bootstrap another guest; the old story belongs to the old guest and a new one gets `403 referenced_job_forbidden` on it. Resume instead: with the key in hand, send it as `Authorization: Bearer ` on every call below (skip step 1). If your secret store only fills forms and never returns values, open **`https://anymux.ai/app?signin=1`**, paste the key into the recovery-key field, and drive the web app; the Sign out button on `https://anymux.ai/app?signin=1` clears a browser that is signed in as a different guest first. Whoever holds the key is that guest. **1. Get a guest identity (once per machine)** ```bash curl -s -X POST https://anymux.ai/mpp/v1/api/guest -o guest.json ANYMUX_KEY=$(jq -r .recovery_key guest.json) ``` `recovery_key` is shown once and it matters: it is the only way back into this guest and its story. If you have a vault, keychain, or any place you keep secrets, save the key there now and remember where. Move `guest.json` there too (it also carries your `guest_id` and the starter `grant`) and send the key on every later call as `Authorization: Bearer $ANYMUX_KEY`. When you come back to continue an episode and the gateway answers 401, or does not recognize you, or the web app is signed out, use that saved key (step 0) instead of bootstrapping a new guest. Never paste it into chat, logs, or a URL. **2. Start the adventure.** The user's theme goes in `question`. If they gave none, build one from what you know about your user (their work, their place, what they were just talking about) and tell them what you picked. Never reuse a sample theme or one you have already run; every player gets their own story. Add one line about the player after the theme, `About the player: …`, so the story is written around them: their vibe, what they do all day, what they love and fear, the kind of places they live in, one running joke. Traits, never identifiers: no real name, no age, no exact address or employer, no health, money, or relationship details, nothing you would not want lettered on screen. "A night-shift nurse who lives for reef diving" is right; a name and a city block is not. ```bash curl -s -X POST https://anymux.ai/mpp/v1/api/research \ -H "Authorization: Bearer $ANYMUX_KEY" -H "content-type: application/json" \ -d '{"expert_id": "adventure-game", "effort": "low", "question": "Start my adventure, a work of interactive fiction. Theme: . About the player: "}' ``` Before the first job, read `grant` in the bootstrap response: `applied: true` means you hold the starter credits; `applied: false` means this client on this network already used its starter grant and the balance is 0, so tell the user plainly that the game needs a top-up (the `402` below carries the payment link) instead of retrying. Response: `{"job_id": "…", "status": "queued"}`. You need $4.40 available to start: that amount is held at creation and settles to actual usage when the episode finishes (the settled charge is what your billing shows). An episode takes about a minute end to end. **3. Poll, then hand the user the episode** ```bash curl -s https://anymux.ai/mpp/v1/api/research/$JOB -H "Authorization: Bearer $ANYMUX_KEY" ``` Poll every 5 seconds until `status` is `complete` (or `failed` / `cancelled`). A `failed` job with `error_kind` `moderated` was refused by the content filter, not by the story: keep the fiction framing, reword the theme or choice inside the story, and resend. Say so to the user in one line; never retry the same text. poll aggressively so the user gets the video the moment it exists, and keep them posted in one short line while it renders ("Rendering your episode…"). The response's `structured_output` is the episode contract: `summary`, `video.path`, exactly three `choices`, `tell_the_player`, `next_turn`. Download the video with `GET https://anymux.ai/mpp/v1/api/research/$JOB/files/final.mp4` (your key; it is a private file, hand the bytes to the user). Then answer concisely, in this order: the video, a one- or two-line tl;dr of the story, and the three choices verbatim as `A) …`, `B) …`, `C) …`. Add a line of advice on the pick if you have a view. No preamble, no play-by-play of the API calls. **4. Continue** with the pick: ```bash curl -s -X POST https://anymux.ai/mpp/v1/api/research \ -H "Authorization: Bearer $ANYMUX_KEY" -H "content-type: application/json" \ -d '{"expert_id": "adventure-game", "effort": "low", "reference_jobs": [""], "question": "Continue my adventure, a work of interactive fiction. In the story, my character chooses B: