> ## 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 <token>; 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.

# Mist

> Mist is Fluid's AI assistant: a desktop app that builds themes, portals, widgets, MySites and apps for your company when you chat with it.

Mist is Fluid's AI assistant, and the admin calls it "Fluid's agentic command center." It's a desktop app for macOS and Windows. You describe what you want in a chat, and Mist plans it, writes it and connects it to your Fluid company.

With Mist you can:

* Build and edit storefront themes, portals, widgets, MySites and hosted apps, called Mist apps.
* Preview your work on your computer, then publish it.
* Ask questions about your company's data, and query your reporting databases.
* Run skills and workflows that automate multi-step jobs, such as opening a country.
* Undo changes Mist made through Time Machine.

## Get started

<Steps>
  <Step title="Download Mist">
    Download the app from the admin, then install it. See [Download Mist](/help/mist/download).
  </Step>

  <Step title="Sign in">
    Sign in with your Fluid email address, then pick a company.
  </Step>

  <Step title="Start a chat">
    Type what you want in the chat, or pick a skill. See [Getting around](/help/mist/getting-around).
  </Step>
</Steps>

## Guides

<CardGroup cols={2}>
  <Card title="Download Mist" icon="download" href="/help/mist/download">
    Install the desktop app, sign in and keep it up to date.
  </Card>

  <Card title="Getting around" icon="compass" href="/help/mist/getting-around">
    The sidebar, the chat, the preview and the title bar.
  </Card>

  <Card title="Chats" icon="comments" href="/help/mist/chats">
    Start, find, pin and rewind your conversations with Mist.
  </Card>

  <Card title="Model selection" icon="microchip" href="/help/mist/models">
    Choose an AI model, or let **Auto** pick one for each message.
  </Card>

  <Card title="Slash commands" icon="terminal" href="/help/mist/slash-commands">
    Every command you can type after **/** in the chat.
  </Card>

  <Card title="Voice" icon="microphone" href="/help/mist/voice">
    Dictate a message, or talk with Mist hands-free.
  </Card>

  <Card title="Pick an element" icon="arrow-pointer" href="/help/mist/pick-an-element">
    Point at part of your preview and tell Mist what to change.
  </Card>

  <Card title="Time Machine" icon="clock-rotate-left" href="/help/mist/time-machine">
    See the changes Mist made to your company and revert them.
  </Card>

  <Card title="Skills" icon="wand-magic-sparkles" href="/help/mist/skills">
    Run, create and schedule reusable instructions.
  </Card>

  <Card title="Workflows" icon="diagram-project" href="/help/mist/workflows">
    Chain skills into multi-step jobs that Mist checks as it goes.
  </Card>

  <Card title="Mist Apps" icon="cubes" href="/help/mist/mist-apps">
    Create hosted apps, themes, portals and other projects.
  </Card>

  <Card title="Run and publish" icon="rocket" href="/help/mist/run-and-publish">
    Preview locally, read logs, publish, and roll back.
  </Card>

  <Card title="Databases" icon="database" href="/help/mist/databases">
    Browse and query your reporting and app databases.
  </Card>

  <Card title="Safe Mode" icon="shield-halved" href="/help/mist/safe-mode">
    Explore and edit locally with no risk of changing production.
  </Card>

  <Card title="Use cases" icon="lightbulb" href="/help/mist/use-cases">
    Examples of what teams do with Mist.
  </Card>
</CardGroup>

## Frequently asked questions

<AccordionGroup>
  <Accordion title="Where do I download Mist?" id="where-download">
    In the admin, open **Settings** > **Developer**, or click the **Developer Hub** code icon in the top bar. Click the **Meet Mist Desktop** banner to download the build for your computer. See [Download Mist](/help/mist/download).
  </Accordion>

  <Accordion title="Can Mist change my live store?" id="change-live-store">
    Yes. Mist can publish themes and apps and make changes through the Fluid API, as you. Turn on [Safe Mode](/help/mist/safe-mode) when you want to explore without any risk of changing production.
  </Accordion>

  <Accordion title="Who pays for what Mist does?" id="who-pays">
    Mist's AI usage is charged to your company, up to a daily cap that Fluid sets. Admins can see the spend on the [AI Spend](/help/admin/settings/ai-spend) screen. Mist apps also use hosting, which appears as Mist usage on [Billing](/help/admin/settings/billing).
  </Accordion>

  <Accordion title="How do I undo something Mist did?" id="undo">
    For a change Mist made through the Fluid API, use [Time Machine](/help/mist/time-machine). For a project's files, use **History** in the preview to roll back. See [Run and publish](/help/mist/run-and-publish#roll-back).
  </Accordion>

  <Accordion title="Where do I manage my company's Mist apps?" id="manage-apps">
    In the admin, on [Mist Apps](/help/admin/settings/mist-apps) under **Settings** > **System**.
  </Accordion>

  <Accordion title="Can I use Mist's skills with other AI agents?" id="skills-elsewhere">
    Yes. Fluid publishes Mist's community skills and workflows in a public repository. Many skills work with other coding agents too. See [Mist Skills](/guides/mist-skills).
  </Accordion>
</AccordionGroup>

## Get help

<Info>
  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.
</Info>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.