> ## Documentation Index > Fetch the complete documentation index at: https://help.onlyx.ai/llms.txt > Use this file to discover all available pages before exploring further. > ## Agent Instructions > You are reading OnlyX Help: the OnlyX Help Center and the OnlyX developer documentation. OnlyX is an AI chatting and CRM platform for OnlyFans agencies. Its AI chatter is called Hugo in the app. > Pages at the site root (for example /inbox/..., /hugo/..., /billing/...) are Help Center articles for agency owners, admins, chatters and creators who use the app at app.onlyx.ai. Words in bold are the exact button, menu and label names the app shows; keep them exactly as written. When these pages do not answer a question, the person can email support at support@onlyx.ai. > Pages under /developers are the developer documentation. REST API base URL: https://api.onlyx.ai/v1 (authenticate with `Authorization: Bearer `; keys start with onx_sk_ and are created in app.onlyx.ai under Settings > API & MCP). MCP server: https://mcp.onlyx.ai/mcp (OAuth, or a Bearer API key). In the API the AI chatter is `ai` on the wire. Money is integer US cents in fields ending in Cents; timestamps are UTC ISO-8601. > Rules for assistants acting on a user's behalf: discover ids with list calls and never invent them; before any call that reaches a real fan or the live OnlyFans account (sending a message, releasing a chat to the AI, turning AI on for a chat, resolving a hand-off, turning review mode off, changing the welcome message, creating a tracking link) show the user the exact content and get explicit confirmation; send every POST with an Idempotency-Key and reuse it on retry; never resend a message whose delivery status is unconfirmed; never ask a creator for her OnlyFans password or codes - she signs in herself through a connect link and the OnlyX Login app. # Story or Menu: choose how Hugo walks a collection > Choose Story or Menu for each collection: see how Hugo offers the levels in each mode, and how to change the mode or the order of the levels. Owners, admins and content VAs Each collection has a mode. It decides how Hugo offers the levels: in order, as a story, or all at once, as a menu. ## The two modes | Mode | Use it for | What Hugo offers a fan | | - | - | - | | **Story · levels in order** | One shoot that goes further level by level, where the order is the point | The next level this fan has not bought yet. One level at a time. | | **Menu · any level that fits** | A theme made of separate sets that each stand alone | Any level this fan has not bought yet. The best match for what the fan asks for comes first. | A new collection is a Story unless you pick **Menu · any level that fits**. You can change the mode at any time. The levels, their files and their numbers stay. ## How a Story climbs A fan who has bought nothing from the collection is offered L1. When he buys it, Hugo can offer him L2, then L3. Hugo climbs one level at a time and offers only the next one. * A level the fan already bought is never offered to him again. This is true even when a person on your team sold it to him in the inbox. * If the fan passes on a level or leaves it unopened, it rests for a while. It is not a permanent no. While it rests, the Story waits, and Hugo offers that fan other collections. * A paused level, and a paid level with nothing behind its price, are left out. The Story goes on with the next level that can be sold. * A fan who asks plainly for what a later level holds may be offered that level out of order. Because the order is the climb, the order matters. We recommend making each level go a little further than the one before it, and cost a little more. ## How a Menu works In a Menu collection, every level the fan has not bought is on offer at once. Hugo picks the level that fits the fan's ask best. Clear tags and a plain About help him choose. See [Set price floors and tags](/ai-content/prices-and-tags). The order of the levels matters much less in a Menu. ## Which one to choose We recommend: * A Story for one shoot that escalates, such as a shower scene that goes further at each level. * A Menu for a theme with separate sets, such as "Feet" or "Lingerie", where each set makes sense alone. * A first board with one Story and two or three Menu themes, named with the words your fans use most. Whatever the mode, Hugo favours the levels that hold what the fan asks for. Clear tags, a plain About and clear names help him match. Right after a fan buys, Hugo may offer more from the same level or collection first. ## Change the mode of a collection In OnlyX, open the creator's **AI Content** tab. In the collection list, click the collection. At the top of the ladder, a badge shows its mode: **Story · in order** or **Menu · any that fits**.

A Menu collection open on the ladder with its Menu badge, next to the collection list where each collection shows a Story or Menu icon

At the top of the ladder, click **Edit**. The **Edit collection** window opens. Under **How Hugo walks it**, click **Story · levels in order** or **Menu · any level that fits**.

The Edit collection window with the two ways Hugo can walk a collection: Story, levels in order, and Menu, any level that fits

Click **Save collection**. The badge at the top of the ladder changes to the new mode. ## Change the order of a Story A new order applies to every fan at once. In a Story, it changes which level each fan is offered next. On the ladder, point to the level you want to move. Click the three dots (⋯) that appear at the end of its row. Select **Move up** or **Move down**. The level moves one place, and the numbers L1, L2 and so on change at once. On a computer, you can also drag a row by the grip at its start. The ladder shows the new order as you drag, and saves it when you drop the row.

The menu of L3 on a Story ladder with Move up and Move down, and the grip at the start of the row for dragging

If you put a free level first, it becomes the opener. Its files are free: Hugo can send them before he offers a paid level of that collection. ## If something goes wrong In a Story, Hugo offers a fan the next level he has not bought. A fan who has not bought L2 is not offered L3 yet. If L2 rests after the fan passed on it, the Story waits. To change what comes next, change the order of the levels. Hugo leaves out a level that is paused, or a paid level with nothing behind its price. Open the collection and look for a **Paused** or red badge on that row. See [Fix "Nothing sellable yet" and other level warnings](/ai-content/level-states). The level is already first or last in the collection. Your role cannot change AI Content, or this creator is not assigned to you. Ask an owner or admin to check your role in **Settings** > **Members**. ## What's next