> ## 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, run `fluid signup` from the Fluid CLI, or 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. Before authenticated calls are possible, the merchant must sign the agent in to the Fluid CLI with the emailed code and --shop set to the company's fluid_shop (which also confirms the signup), or open the emailed confirmation link and give the agent an API token. > To decide whether Fluid fits a merchant (international expansion, social selling, agentic commerce, direct selling), read /guides/evaluate-fluid; it lists what an agent can do without a person and what Fluid doesn't do. Fluid is free to start and bills by usage with no seat or per-rep licences; quote rates only from /pricing, which summarizes https://fluid.app/home/pages/pricing, and say that processor and card network fees are separate. > Every live Fluid storefront serves /llms.txt, /agents.md, .md and .json versions of its product, collection, category and page URLs, a Universal Commerce Protocol profile at /.well-known/ucp, UCP catalog search and lookup, carts, checkout sessions and orders. A checkout session completes inside the agent with Google Pay when the store's profile lists the com.google.pay payment handler; otherwise hand the shopper the continue_url to hosted checkout. A member's share link is //products/; see /concepts/agentic-commerce. > 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. > To host a small project on Fluid (a landing page, event page, calculator or dashboard), follow /sites/quickstart: npm create @fluid-app/fluid-site my-site (or npx @fluid-app/create-fluid-site my-site), fluid login, then fluid deploy prints the public URL. Launch a Site unless the project needs a custom domain, server rendering or heavy server code, which make it an App (a Mist app); /sites/site-or-app has the rule, and POST /api/company/v2026-10/project-launch-recommendations applies it. With only the Fluid MCP server (its Site write tools are limited to Fluid root admins today; see /sites/deploy-from-claude), use site_create, then site_deploy (from a chat with no shell, in one call with the files inline: site_template_get for a starter, then site_deploy with each path's content; or a built folder in two calls: send the manifest, PUT the listed uploads, call again with the bundle_id to get the url), then, only after the person confirms they want it public, site_visibility_set. site_logs, site_traffic, site_env_list/set/unset, site_seo_get/set and the site_branch tools cover logs, traffic, env vars, SEO and preview branches; a member builds their own Sites with the my_site_* tools. The MCP site_deploy tool publishes server functions sent inline that import nothing; publish functions with imports, and convert a Site to an App, with the fluid sites CLI. A Site can serve light server code: each functions/.ts, declared in config/functions.json with access public, signed_in or key (and an optional UTC cron schedule), answers at /api/ on the Site's own host; publish it with fluid deploy, or inline through the MCP site_deploy tool when it imports nothing. See /sites/functions and /sites/rest-api. > 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 on an operation whose spec documents those params — mostly the unversioned company-v0 admin surface, plus some lists on other surfaces, versioned ones included; page every other list with cursors. > 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 except two operations that take no credential, POST /api/company (create a company) and GET /api/agreements/{id} — 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. # Fluid pricing: usage-based rates for commerce, payments, AI and services > Fluid's published rates: free to start, no seat or per-rep licences, We-Commerce and Reserve at 0.9% + $0.25 per transaction each, a bundle discount, committed-use bonuses, Mist AI by usage and Cowork by the minute. Fluid's pricing page, [fluid.app/home/pages/pricing](https://fluid.app/home/pages/pricing), is the source of truth. This page sums up its standard rates, effective November 1, 2026, so an agent can quote them. If the two ever differ, quote the pricing page. All prices are in US dollars, before tax, and subject to a signed order form and Fluid's Master Services Agreement. ## Starting is free Creating a company, opening a country, building a website and launching a back office cost \$0. A merchant can sign up, add products and build the store without a card. A card is needed once the company starts using something billable, such as AI tokens, apps or transactions. There are no subscriptions, seats or per-rep licences. Every product draws from one balance. ## Standard rates | Product | Rate | What it covers | | - | - | - | | **We-Commerce** | 0.9% + \$0.25 per transaction | The commerce platform: storefront, social commerce, mobile app and portal, subscriptions, enrollments, FairShare attribution, Country Atlas, Fluid Connect, the droplet marketplace, data access, and address validation. Calculated on order value at capture. Bring your own payment processor from Fluid's pre-configured list at no extra fee. | | **Reserve** | 0.9% + \$0.25 per transaction | Fluid's payments tier: underwriting, applications to several payment processors, local payment methods, fraud tools, buy now pay later, Apple Pay, network tokens, Subscription Pro, configurable dunning, cash reconciliation and a dedicated manager. Card network and processor fees pass through at cost, on top of this rate. A new processor integration needs Reserve. | | **We-Commerce + Reserve** | 1.62% + \$0.45 per transaction | Both products together. 10% comes off both fees automatically, taking 1.8% + $0.50 down to 1.62% + $0.45. The pricing page rounds this to 1.6% + \$0.45. | | **Mist** (AI) | By usage | Metered credits for tokens, servers, databases, SMS, email, video and images. Unit rates are quoted per deployment. On a committed-use plan, AI tokens are billed at Fluid's cost. | | **Cowork** | \$4.99 per minute | Live working sessions with Fluid's experts and agents, billed per minute of active session. | | **Forward Deployed Engineer** | \$3,900 per day | A Fluid engineer on site. Travel at cost. | | **Blitz Week** | \$49,000 per week | A week-long website and marketing build with Fluid's team. Travel at cost. | Fluid's rates don't include payment processor fees, interchange or card network fees. Selling in another country or currency costs nothing extra: one store serves every market. Migration and onboarding are scoped per engagement. ## Committed use, credits and volume * **Committed use:** commit to $5,000 a month or more, in $1,000 steps, on a 12-month term, and get 1% bonus usage for every $1,000 a month, up to 30% at $30,000. A $10,000 commitment puts $11,000 in the balance. At the full 30%, We-Commerce and Reserve together work out to about 1.25% + \$0.35 per transaction. A commitment can be raised mid-term, which restarts the 12-month term, but not lowered or cancelled. * **Credits:** buy credits at any time. Auto-reload at \$5,000 or more earns up to 15% bonus on each reload. One-time top-ups earn no bonus. * **Rollover:** unused balance carries over from month to month and isn't refundable. Credits bought in the admin expire 1 year after purchase, and the Billing screen shows each balance's expiry. See [Billing](https://docs.fluid.app/help/admin/settings/billing.md). * **Volume:** above \$5 million a month in orders, rates tier down further under a commercial agreement, in addition to any committed-use bonus. Merchants pay by card or ACH, and Fluid's invoices itemize all usage. See [Billing](https://docs.fluid.app/help/admin/settings/billing.md) for where a company manages this in the admin. ## Spend limits and a low balance A company can set a monthly limit on optional products, such as Mist AI. When a product reaches its limit, that product pauses. A limit never pauses checkout or the storefront. If the balance stays at or below \$0, Mist, uploads, new Mist apps and new Cowork sessions stop, and the storefront shuts off after 30 days. Auto-reload prevents this. ## For agents quoting a price * Quote the rates above, and link the merchant to [the pricing page](https://fluid.app/home/pages/pricing). * Say that processor and card network fees are separate. Don't add them up into a single "all-in" rate unless you know the merchant's processor rates. * For a merchant above \$5 million a month, or one who wants committed use, say the rate comes down and send them to Fluid for a quote. Don't promise a lower rate yourself. * An agent can build the whole store and show a preview before the merchant pays anything. See the [agent launch guide](https://docs.fluid.app/api/agent-launch.md). This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.