> ## 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. # Coming soon > What the OnlyX API and MCP server do not do yet, and what is on the way: webhooks, mass messages, vault uploads, posts, account lifecycle, money, promotions, team metrics and developer tooling. OnlyX API v1 covers creators and connecting, the inbox and sending, hand-offs, fans, vault media, statistics, the AI chatter's persona, content and settings, and tracking links. This page lists what it does **not** do yet, so you can plan around it. This is a list of plans, not promises or dates. When something ships it moves to the [changelog](/developers/changelog) and the [API reference](/developers/api-reference/introduction). **Tell us what you need: [developers@onlyx.ai](mailto:developers@onlyx.ai).** Requests from real integrations decide the order. ## Already available in v1 Some of what agencies ask for is already here, and much of it is not offered anywhere else: Read and edit the brief the AI chatter follows for each creator, field by field. Build the priced levels the AI sells from, with preview and paid media. Take over, release, or switch the AI off for a single conversation. See every chat the AI handed to your team, and why, and resolve it. Operate OnlyX from Claude, ChatGPT, Cursor or VS Code in one click. A one-time link: the creator signs in herself, face check included. Also in v1: scoped, workspace-owned API keys that can be limited to some creators; an `Idempotency-Key` on sends, creates and every other write that can reach a fan, so retries never double-send; fan notes, custom names and mute; tracking-link cost, profit and ROI; and rate-limit headers on every authenticated response. ## Webhooks and events * **Webhooks.** OnlyX will call your URL when something happens: a fan message arrives, a paid message is unlocked, a tip or a new, renewed or expired subscription comes in, or a transaction is recorded. * **AI events.** You will be told when the AI hands a chat off, when the AI is switched on or off, and when review mode holds a reply. * **Account health events.** An event when a creator's OnlyFans session ends, needs a code or a face check, or the account is restricted, so you can react before fans notice. * **Signed deliveries with retries.** Every webhook will be signed so you can verify it came from OnlyX, retried with backoff, and listed in a delivery log you can replay from. Until then, poll: `GET /v1/conversations?unread=true`, `GET /v1/handoffs` and `GET /v1/creators/{creatorId}/connection` are cheap and made for it. ## Messaging * **Mass messages.** Send one message, free or paid, to a fan list or a segment, with exclusion lists. (The AI's own scheduled list messages are visible read-only in `GET /v1/creators/{creatorId}/ai-settings` today.) * **Scheduled messages.** Queue a message to one fan or a list for a later time, and list, edit or cancel what is queued. * **Unsend.** Take back a message within the window OnlyFans allows. * **Message search.** Find messages by text across a creator's inbox, not only fans by name. * **Paid-message analytics.** Who bought each paid message and how every mass message performed. ## Vault * **Vault uploads.** Upload photos and videos to a creator's vault from a file or a URL, then use the new media ids in messages and levels. * **Vault organization.** Create vault lists, move media between them, and hide or delete media. ## Posts, stories and the queue * **Posts.** List, create (with media, price and expiry), schedule, edit and delete wall posts, with their likes, comments and tips. * **Stories and highlights.** Post stories, see viewers, and manage highlights. * **The scheduled queue.** See and manage everything scheduled for a creator, posts and messages together. ## Fans * **Fan list management.** Create, rename and delete OnlyFans fan lists, and add or remove fans. * **Tags.** Tag fans with your own labels and filter by them. * **Block and restrict.** Block, restrict or unrestrict a fan on OnlyFans, and list who is blocked or restricted. * **Subscription history.** Every past subscription, renewal and price for a fan. ## Creator accounts * **Disconnect and reconnect.** End a creator's OnlyFans session, or start a fresh sign-in, from the API. * **Delete a creator.** Remove a creator and her data from your workspace through the API. * **Adding Telegram creators.** Telegram creators already appear in the API with `platform: "telegram"`; adding and connecting one through the API is coming. Today you add them in the dashboard ([Telegram creators](/telegram)). * **Profile settings.** Update her name, bio, avatar, header and subscription price. ## Money * **Balances and payouts.** Current, pending and available balance, and payout history. * **Chargebacks.** Chargebacks with the fans and amounts involved, and the chargeback ratio. * **Buyers per tracking link.** The fans each tracking link brought and what each of them spent. * **Data exports.** Download transactions and fans as CSV for accounting. ## Promotions * **Promotions and discounts.** Create and stop subscription promotions and per-fan discounts. * **Trial link extras.** See who claimed a trial, and deactivate or delete trial and tracking links. * **Bundles.** Create and edit subscription bundles. ## Team * **Chatter performance.** Sales, reply times and conversion per team member, beside the AI's. * **Shifts.** Shifts, clock-in and timesheets for chat teams. ## Developer tools * **SDKs.** Official TypeScript and Python clients generated from the OpenAPI document. * **Sandbox and test mode.** Test keys with fixture creators and fans, so you can build without touching a real account. * **No-code connectors.** Zapier, n8n and Make integrations built on the webhooks. * **Interactive API reference.** A "Send" button on every reference page to try calls with your key, arriving with the API launch. ## Tell us what you need Write to **[developers@onlyx.ai](mailto:developers@onlyx.ai)** with what you are building and which of these would unblock you, or anything missing from this list. Include an example of the call you wish existed; it helps us shape it.