> ## 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.
> Lists use cursor pagination via the page[cursor] and page[limit] query params; follow meta.pagination.next_cursor until it is null.
> Never use /api/company/v1 or /api/v1 paths, page/per_page params, or offset pagination — they are legacy.
> 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).
> Successful responses wrap the resource payload alongside a top-level integer status and a meta object.

# Fluid: The We-Commerce Platform for Direct Sales Teams

> Fluid is a We-Commerce platform combining e-commerce and direct sales tools. Learn how Fluid helps merchants and reps sell together with full transparency.

Fluid is a We-Commerce platform built for merchants and direct sales teams who want to sell together — not in silos. It unifies your storefront, sales rep attribution, global payments, and customer identity into a single connected system, so every party in a sale gets full credit and visibility. Whether you're launching a new product, onboarding a network of reps, or expanding into new markets, Fluid gives you the infrastructure to grow without stitching together dozens of third-party tools.

<CardGroup cols={2}>
  <Card title="Quickstart" icon="rocket" href="/quickstart">
    Set up your account, install FairShare, and make your first API call in under 10 minutes.
  </Card>

  <Card title="Platform Overview" icon="map" href="/platform-overview">
    Explore every component of the Fluid platform and understand how they work together.
  </Card>

  <Card title="SDK Overview" icon="code" href="/sdk/overview">
    Integrate FairShare attribution and Fluid's client-side tools into your existing website.
  </Card>

  <Card title="API Overview" icon="webhook" href="/api/overview">
    Browse the full Fluid REST API — products, orders, customers, commissions, and more.
  </Card>
</CardGroup>

## Key Platform Components

Fluid is composed of several purpose-built modules that work independently or together. Here's a quick orientation to the most commonly used components.

### FairShare Attribution

FairShare is Fluid's JavaScript attribution SDK. It tracks which sales rep deserves credit for a purchase by following cookies, fingerprints, and referral routes — even across domains you don't own. Install one script tag on any site and FairShare silently attributes every conversion back to the right rep.

### Fluid Payments

Fluid Payments is a global payment aggregator that supports 300+ alternative payment methods (APMs) across 100+ countries. Accept Apple Pay, Google Pay, GCash, AliPay, local bank transfers, and dozens of regional wallets without managing separate payment processor accounts. All card data is stored in Fluid's PCI-compliant vault.

### We-Commerce Checkout

Fluid's one-page checkout lives at [checkout.fluid.app](https://checkout.fluid.app) and is shared across every Fluid-powered storefront. Returning customers check out instantly using saved profiles, reducing cart abandonment without any extra development work on your end.

### Website Editor

The Website Editor is a drag-and-drop site builder that uses Liquid templating. Start from one of three themes — Base, Vox, or Fluid — and customize your storefront without writing a line of code. Developers can drop into the template layer at any time for full control.

### Droplet Marketplace

Droplets are pre-built third-party app integrations you can add to your store with a single click. Because every Droplet is built against Fluid's native APIs, they work seamlessly with your checkout, rep attribution, and commission engine — no middleware to configure or maintain.

## Need Help?

If you run into issues or have questions about your account, the Fluid team is here to help.

* **Email support:** [support@fluid.app](mailto:support@fluid.app)
* **Admin dashboard:** [admin.fluid.app](https://admin.fluid.app)
