> ## 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. > 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. /api/company/v1 and /api/v1/... paths are documented in no spec here and must never be used (/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. > Navigation menu management is documented in themes/navigation-menus. These unversioned admin endpoints (/api/menus and nested menu_items) are verified against the implementation but are not yet in the synced OpenAPI specs. Use that reference for menu payloads and its flat page/per_page pagination; missing spec coverage does not make these endpoints unavailable. > 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/auth-v0.yaml covers the unversioned auth surface (/api/... paths — authentication, MFA, social auth, and token exchange); 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. # Show member prices > Render member-specific prices from ordinary Liquid price expressions in a cached theme. With the member storefront enabled, ordinary price expressions become member-aware on their own. You do not need a special tag for the common case. ```liquid theme={null} {{ product.price }} {{ variant.price }} ``` Each visible price expression renders a price shell that already contains the guest price. The runtime then asks Fluid for the signed-in member's price and replaces the text. Guests keep the price your theme rendered. The server decides the member's tier and formats the money. The browser only writes text — it never picks a tier or calculates an amount. ## What stays a plain value Only prices you display become shells. A price used as data stays an ordinary Liquid value, so your logic keeps working: | Use | Result | | ------------------------------------------------------------- | ------------------ | | Visible output, such as `{{ product.price }}` | Member price shell | | A condition, such as `{% if product.price > 5000 %}` | Plain value | | An HTML attribute, such as `data-price="{{ product.price }}"` | Plain value | | JSON or captured strings | Plain value | This means sorting, comparisons, and structured data keep the guest price. Only what a member reads on the page changes. ## Apply filters to a price Filters on a visible price are replayed against the member's price by Fluid, then the result is written back as text. ```liquid theme={null} {{ product.price | times: 0.9 | money }} ``` Filters applied through an assignment compose with filters on the final output: ```liquid theme={null} {% assign product_price = product.price | replace: '$', 'USD ' %} {{ product_price | append: ' each' }} ``` Supported transformations include arithmetic (`plus`, `minus`, `times`, `divided_by`, `modulo`), rounding and bounds, `money`, `default`, escaping, and scalar text operations such as `append`, `prepend`, `replace`, `remove`, case conversion, trimming, and truncation. Filters preserve ordinary Liquid semantics. Arithmetic on an already formatted price string behaves exactly as it would on that string anywhere else, and a numeric price stays numeric. ### Limits A replayed filter chain accepts at most: * 12 filters * 3 scalar arguments per filter * 512 bytes per string argument Filter arguments are evaluated by Liquid while your page renders. They are never executed as code by Fluid. Filters that load resources, generate HTML, or depend on request context are excluded. An expression using one keeps its original output rather than becoming a member price. ## Place a price shell yourself Use the `member_price` filter when you need a shell somewhere an ordinary price expression will not reach: ```liquid theme={null} {{ product | member_price }} ``` This remains supported alongside automatic shells. ## Country and variant A price shell carries the product, the selected variant, and the storefront country. Change the variant or country on the element and the runtime fetches the matching price again. Omit the variant and Fluid prices the product's default variant. ## When a price does not resolve The shell keeps the guest price whenever Fluid cannot return a member price: * The member has no price for that product * The response is missing, invalid, or times out * The session expired — every shell on the page reverts to its guest content Bundles that cannot be priced for a member return no price, so your Liquid range stays intact. A genuine zero is formatted and shown. Identical requests are deduplicated until the next session refresh, so repeating the same product on a page costs one lookup.