> ## 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. > 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/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. # AI Spend > See today's AI spend against your company's daily cap, and review your spend history by time frame, provider and type. This screen shows the AI spend charged to your company: today's spend against your daily cap, and your spend history over time. It has no settings to change. ## Where to find it In the admin, click the **Settings** gear in the top bar. In the Settings sidebar, under **Payments**, select **AI Spend**. To open the screen, your role needs at least **View only** for **Mist**, in the **Other** card on the role's **Permissions** tab. Without it, **AI Spend** doesn't appear in the Settings sidebar. The same permission also shows **Mist Apps** in the sidebar. You manage roles on the [Roles](/help/admin/settings/roles) screen. ## What's on the screen All amounts are in US dollars. Each day on this screen runs from midnight to midnight UTC. ### Today's AI spend At the top of the screen: * **Daily cap**: the cap on your company's AI spend for each day. Fluid sets it. * **Today**: how much your company has spent on AI so far today, out of the daily cap, and how much of the cap remains. * A bar that fills as today's spend nears the cap. It changes color when today's spend reaches 70% of the cap, and again at 90%. The line under the bar reads "The cap resets at midnight UTC." ### Usage The **Usage** card shows your AI spend history for the time frame you select. At the top of the card, **Time frame** sets the days the card covers: * **This month**: from the first day of the current month through today. * **Last 30 days**: today and the 29 days before it. This is the time frame you see when you open the screen. * **Last 90 days**: today and the 89 days before it. * **All time**: from your company's first recorded day of AI usage. You can't select it until your company has AI usage. * **Custom**: dates you pick on a calendar. **By provider** and **By type** narrow the card to some AI providers, or to some types of AI usage, such as **Chat turn** or **Image generation**. Both filters appear once the time frame's data loads, and only when the time frame has AI usage. Each one lists only the providers or types with usage in that time frame. Below the controls, **Daily spend** shows the dates of the time frame, then: * **Charged**: the total AI spend charged to your company in the time frame, for the providers and types you've filtered to. * A bar chart with one bar per day for that day's charged spend. Days without AI usage show as zero. Hover over a bar to see its date and amount. If the time frame has no AI usage, the card reads "No AI usage in this period." instead of showing the chart. When you switch time frames, the current figures stay on screen, dimmed, until the new ones load. ## Choose custom dates Under **Time frame**, click **Custom**. A calendar opens, showing two months. Click the day the window starts, then the day it ends. You can't pick days before your company's first recorded AI usage, or days after today. The calendar closes and the card shows your dates. Next to the time frames, a button shows those dates. Click it to pick new dates. If you close the calendar before you pick the last day, the card keeps the time frame it had. ## Filter by provider or type Click the menu under **By provider** or **By type**. Both start at **All**. Select each provider or type you want to include. The menu stays open, so you can pick several. Select **All** to clear your picks. **Charged** and the chart update right away. The menu shows the name you picked, or how many you picked, such as **2 selected**. Choosing a new time frame resets both filters to **All**. The filters don't change the daily cap or today's spend at the top of the screen. ## Frequently asked questions No. Fluid sets your company's daily cap, and this screen only shows it. To ask about your cap, see [Getting help](/help/getting-help). UTC, whatever your own time zone. Today's spend, the cap's reset at midnight, and each day in the **Usage** card all follow the UTC calendar. They appear only when the selected time frame has AI usage. Pick a time frame that includes some AI usage. ## Related pages * [Settings](/help/admin/settings) * [Roles](/help/admin/settings/roles) * [Billing](/help/admin/settings/billing) * [Mist Apps](/help/admin/settings/mist-apps) This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.