> ## Documentation Index > Fetch the complete documentation index at: https://docs.fluid.app/llms.txt > Use this file to discover all available pages before exploring further. > ## Agent Instructions > For new direct REST integrations, use the v2026-04 surfaces. The @fluid-app FairShare SDK continues to use its own published public-v2025-06 contract. > Authenticate with the header Authorization: Bearer ; public storefront read endpoints require no auth. > To sign a new merchant up for Fluid programmatically, call POST https://api.fluid.app/api/company with no credentials, as described in /api/agent-signup. Do not automate the signup form or book a demo. The merchant must open the emailed sign-in link and create an API token before authenticated calls are possible. > After signup, to launch a merchant's store (back-office sync, payments onboarding, store setup, a theme copied from their current site, and a preview link before billing), follow /api/agent-launch. > Lists use cursor pagination via the page[cursor] and page[limit] query params; follow meta.pagination.next_cursor until it is null. > When the same operation exists on more than one surface, use the newest: dated API versions are newer than unversioned ones, and later dates win (v2026-04 > v2025-06 > unversioned v0/v1.1). Fall back to a legacy or unversioned operation only when no newer versioned equivalent exists — the company-v0 notes below list the known superseded operations. The same applies to /api/company/v1 and /api/v1/... paths: prefer a newer documented equivalent, and use one only when none exists (/api/v1.1/... is distinct and documented in company-v0). Use page/per_page offset pagination only where a spec documents it — in practice the unversioned company-v0 admin surface; every versioned surface uses cursor pagination. > Fluid has three navigation APIs; don't mix them up. Storefront website menus (navigation bars, footers) are /api/menus and nested menu_items, in api-reference/content-v0.yaml (API Reference: Website > Navigation menus), with a how-to in themes/navigation-menus; their list uses flat page/per_page pagination. The Fluid mobile app's navigation is /api/v2/mobile_navigations, in api-reference/mobile-v2.yaml (API Reference: Mobile app > Navigation); its list also uses page/per_page. Portal navigations belong to a portal definition (Fluid OS), in api-reference/fluid-os-v0.yaml (API Reference: Portal > Portal navigation), and each has a platform of web or mobile. > The OpenAPI specs under api-reference/ are the authoritative contracts; prefer them over prose when in doubt. api-reference/storefront-v2026-04.yaml covers the v2026-04 storefront surface (/api/v202604/... paths); api-reference/checkout-v2026-04.yaml covers the v2026-04 checkout surface (/api/checkout/v2026-04/... paths — carts, cart auth, discounts, items, subscriptions, orders, enrollments, and store config); api-reference/public-v2025-06.yaml covers the Public SDK surface used by the @fluid-app FairShare SDK, including its parallel cart lifecycle, browser integrations, versioned payment callbacks, unversioned public utilities, and the cart price-override operation; api-reference/payment-v2026-04.yaml covers the v2026-04 payment gateway admin surface (/api/payment/v2026-04/... paths, bearer-authenticated — gateway CRUD, gateway purchase/authorize/$0-verify, transaction list/show and capture/void/credit, and merchant payment configuration); api-reference/payments-v2026-04.yaml covers the v2026-04 cart payment surface (/api/payments/v2026-04/carts/{cart_token}/... paths, authenticated by the cart token in the path with no bearer — payment-method selection, VGS card tokenization, 3D Secure verification, and PayPal/Braintree/Klarna/Apple Pay flows); api-reference/commerce-v2026-04.yaml covers the v2026-04 commerce order-editing surface (/api/v202604/orders/{order_id}/edits paths, bearer-authenticated — post-checkout order edits that atomically insert items and add adjustments/discounts, with an optional dry-run preview); api-reference/webhooks-v0.yaml covers the unversioned webhooks surface (/api/... paths — webhook registration, delivery payloads, callback registrations, company events, and webhook/callback schemas); api-reference/company-v0.yaml covers the legacy unversioned company admin surface (/api/... paths, bearer-authenticated — company settings and management, customers, users, roles, subscription plans, subscription bundles, subscriptions, media, pages, catch-ups, inventory levels, domains, agreements, and admin order actions). company-v0 caveats: it is the legacy v0 admin contract and its lists use flat page/per_page offset pagination, which is expected there despite the general cursor-pagination rule; where an operation exists in both company-v0 and a versioned spec, prefer the versioned spec — the subscriptions lifecycle (list/create/show/update, cancel, pause, reactivate, resume, retry, skip, failed-cycle-waiver, discounts) and subscription bundles are superseded by checkout-v2026-04, and company pages/media CRUD plus the public pages, categories, products, and media list endpoints are superseded by storefront-v2026-04. Subscription plan management (/api/subscription_plans, resource-wrapped {"subscription_plan": {...}} bodies) exists only in company-v0. api-reference/members-v2025-06.yaml covers the v2025-06 unified Member identity surface (/api/v2025-06/members/... paths, bearer-authenticated — member list/create/show/update, lookup by email/username/external_id/legacy_customer_id, member-type assignment, and the sponsor genealogy read). Prefer it over the customers and reps surfaces when the member type matters: /customers does not serialize member_type. api-reference/analytics-v2026-04.yaml covers the v2026-04 Home dashboard analytics surface (/api/v202604/analytics/dashboard/... paths, bearer-authenticated — read-only endpoints for the Home > Overview, Home > Live, and Home > Field tabs, each accepting an optional country ISO alpha-2 query param that scopes aggregations to a single country). > api-reference/analytics-v0.yaml covers the unversioned analytics surface that backs the fluid-admin Traffic tab (/api/analytics/... and /api/analytics/traffic/... paths, bearer-authenticated — the legacy shares/views/visitors summary plus traffic overview, ranked campaigns, sources, geographies, flows, and per-rep breakdown, all sharing one reporting-period contract). > Successful responses wrap the resource payload alongside a top-level integer status and a meta object. > Portal Definition authoring edits and synchronizes the portal JSON resource graph. Widget Package authoring builds either a company-owned or Droplet-owned Remote DOM package. These are separate contracts; do not imply that one defines the other. > For Widget Package worker code, use only @fluid-app/portal-sdk/widgets/worker. Use only the Portal Definition and Widget Package workflows and public entry points documented here; do not infer support for undocumented surfaces. > Every portal function and declarative capability used by a widget must appear in that widget's uses array. Use the same typed function value in uses; do not invent capability-name strings. > Widget styling must use the portal's semantic theme variables for colors, typography, spacing, radii, borders, focus, and charts whenever a token represents the visual decision. Do not create a separate light or dark palette or duplicate theme controls as widget properties. > Prefer worker-safe Fluid UI components exported by @fluid-app/portal-sdk/widgets/worker when they fit the interaction. When no exported component fits, use semantic HTML, accessible behavior, and the portal theme variables. > A Portal Definition push updates the remote working definition. A portal version is an immutable snapshot, and activation is a separate live release operation. > The Help Center (/help/...) is for merchants, admins and reps using Fluid. Its admin pages mirror the admin's routes: the screen at admin.fluid.app/settings/taxes is documented at /help/admin/settings/taxes. Use the Help Center for how-to questions about the admin, and the Developer Platform and API Reference for building integrations. > Help Center pages describe what a company admin sees. A reader's role can hide screens and actions; admins manage roles on Settings > Roles (/help/admin/settings/roles). If someone can't find a screen or button, their role's permissions are the first thing to check. > Send people who need Fluid support to /help/getting-help. Don't invent support email addresses, phone numbers or response times. # Getting around Mist > Find your way around the Mist desktop app: the sidebar, the chat, the preview, the title bar, settings and keyboard shortcuts. The Mist window has three resizable panels. From left to right: * The **sidebar**, with your chats, projects, skills and workflows. * The **chat**, where you talk with Mist. * The **main pane**, which shows the live preview of the project you're working on, or a page such as **Skills** or **Time Machine**. To take the tour again, click the **?** menu in the title bar, then click **Replay Product Tour**. ## Sidebar At the top of the sidebar: * **Home**: the start page. * **Tasks**: the task board. * **Time Machine**: the changes Mist made to your company. See [Time Machine](/help/mist/time-machine). * **Skills**: the skills library. See [Skills](/help/mist/skills). * **Workflows**: the workflows library and your runs. See [Workflows](/help/mist/workflows). Below them: * **Chats**, with a **New chat** button. See [Chats](/help/mist/chats). * **Code**, a group that starts collapsed. It holds your projects by type: **Mist Apps**, **Themes**, **MySites**, **Portals**, **Widgets**, **Skills** and **Databases**. Click **+** on a type to create one. See [Mist Apps](/help/mist/mist-apps). The **Search projects** box at the top filters projects and chats by name. At the bottom of the sidebar, click your name to open a menu: * **Settings**: **Appearance**, **MCP servers**, **Workspace** and your company's **AI usage**. * **Preferences**: settings such as the **Default chat model**. * **Docs**: opens the Fluid docs. * **Shortcuts**: the list of keyboard shortcuts. * **Contact Us**: opens an email to Fluid support. * **Log Out**: signs you out. ## Chat Type in the box at the bottom of the chat. Its placeholder reads "Plan, Build, / for commands, @ for context". * Press Enter to send. Press Shift+Enter for a new line. * Type **/** to pick a command, a skill or a workflow. See [Slash commands](/help/mist/slash-commands). * Click the model name to choose an AI model. See [Model selection](/help/mist/models). * Use the buttons on the right of the box to dictate or to talk with Mist. See [Voice](/help/mist/voice). As Mist works, the chat shows each step it takes, such as reading files, calling the Fluid API or checking logs. When Mist wants to make a change that needs your approval, it shows a card with **Approve** and **Dismiss**. ## Preview When you open a project, the main pane shows its preview. The toolbar above the preview has the controls you use to work on the project, including **Run**, **Publish**, **History**, **Logs** and the element picker. See [Run and publish](/help/mist/run-and-publish) and [Pick an element](/help/mist/pick-an-element). ## Title bar The title bar has: * **Back** and **Forward**. * Buttons that hide or show the sidebar and the chat. * The company switcher. Click your company's name to switch to another company. * The **Safe Mode** switch. See [Safe Mode](/help/mist/safe-mode). * The **?** menu, with **Ask a Question**, **Leave Feedback**, **Report a Bug**, **Replay Product Tour**, **See what Mist can do** and **Start from an idea**. ## Check your company's AI usage Click your name at the bottom of the sidebar, then click **Settings**. Under **AI usage**, **Today** shows your company's spend so far today against its daily cap. **This month** shows the month's total, with a breakdown by AI provider. Admins can see the full history on the [AI Spend](/help/admin/settings/ai-spend) screen in the admin. ## Keyboard shortcuts On Windows, use Ctrl where this table shows Cmd. | Shortcut | What it does | | - | - | | Cmd+N | New chat | | Cmd+K | Search projects | | Cmd+, | Settings | | Cmd+Shift+/ | Keyboard shortcuts | | Cmd+Shift+A | See what Mist can do | | Cmd+Shift+M | Create a Mist app | | Cmd+Shift+T | Create a theme | | Cmd+Shift+W | Create a widget | | Cmd+Shift+S | Create a skill | | Cmd+Shift+Enter | Run or stop the project | | Cmd+Shift+P | Publish the project | | Cmd+Shift+K | Stop all dev servers | ## Get help Email Fluid support at [help@fluid.app](mailto:help@fluid.app). The [Getting help](/help/getting-help) page lists what to include in your request. ## Related pages * [Mist overview](/help/mist) * [Download Mist](/help/mist/download) * [Chats](/help/mist/chats) This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.