firmly funding, valuation and investors

Product & use cases

A merchant or online retailer authorizes firmly to connect with its existing e-commerce environment; firmly retrieves product catalog and live stock, and exposes standardized discovery, cart and payment flows to authorized shopping destinations. A publisher, AI assistant or marketplace integrates once with firmly rather than implementing a new checkout for each merchant. For a merchant's own site, Ask Agent can be installed through a JavaScript snippet; shoppers describe needs conversationally, receive current catalog-based product suggestions, choose an item and check out through the existing merchant's payment rails. The merchant—not firmly—remains the merchant of record, handles shipping, taxes, returns and customer service according to the applicable contract. A third-party destination needs an issued App ID for sandbox/test merchant access. Pricing not listed publicly; no independent security, reliability or conversion-effectiveness audit located.

• Merchant onboarding (illustrative): authorize one connection to the existing ecommerce stack, confirm product/catalog and inventory synchronization, approve destinations and test checkout; the merchant retains order ownership.
• Publisher or agent integration (documented): obtain a sandbox App ID from firmly, query an approved merchant's catalog, create a cart, collect shipping/payment information and submit an order via Standard /api/v1.
• Advanced retail destination (documented): use /api/v2 for supported merchants needing split shipments, delivery scheduling, pickup or add-ons; capability depends on merchant support.
• Shopper (illustrative): ask an onsite Ask Agent for a bag under a budget, compare actual in-stock products, select an item and complete an in-chat checkout without leaving the retailer's website.
• Buyer diligence: test catalog latency, multi-merchant consents, payment disputes, order cancellations, data access and real net fees before accepting promotional conversion claims.

Key facts

• $15M Series A announced November 5, 2026; Squarepoint Capital led; approximately $20M cumulative disclosed financing.
• Other participants include J.P. Morgan Payments, Mastercard, Samsung NEXT, Alumni Ventures, ARK Invest, Benhamou Global Ventures, Granada Funds, Hike Ventures, The Mercantile Companies and Versus Ventures.
• Firmly Connect preserves existing merchant payment processor, customer ownership, inventory and merchant-of-record responsibilities.
• Firmly says its infrastructure can reach 11M+ merchants and merchants generating $900B+ GMV. This is not firmly's processed volume or revenue.
• Ask Agent launched alongside the Series A, with early selected merchant deployments reporting up to 18% conversion and 23% average-order-value uplift; samples and independent attribution not published.
• Pricing, revenue, valuation and transaction take-rate were not publicly disclosed.

Competitive landscape

Edge: One merchant-approved connectivity layer across commerce stacks and destination APIs; reduces custom merchant-side integrations and leaves merchant-of-record status with the retailer. This is a vendor-described differentiator, not an independently verified universal integration claim.

Firmly aims to abstract over existing retailer commerce stacks and competing agent protocols. Its difference is who builds the integration and who owns the sale, not a proven guarantee of universal channel compatibility. Buyers should compare supported platforms, merchant authorization, cart/fulfillment needs, data usage policies and true per-transaction fees. Do not treat the '11 million merchants / $900B GMV' addressable reach figure as actual Firmly-processed sales.

• Shopify / Shopify Catalog and agentic checkout tools adjacent

  Native commerce-platform ecosystems can provide direct catalog and checkout integrations; merchants outside that ecosystem still need adapters.

• Google Universal Commerce Protocol (UCP) alternative

  An open agent-commerce protocol, not a vendor itself; stores can implement directly at engineering cost.

• Stripe Agentic Commerce Protocol (ACP) alternative

  Protocol/infrastructure path for agent checkout, with different payment integration and merchant responsibilities.

• Browser-agent checkout (e.g. AI assistant web automation) alternative

  Can interact with existing storefronts but may be more brittle and require browser permissions.

• Retailers' own integration and API teams incumbent

  Custom integrations preserve control but are costly to maintain across multiple channels.

Market / IPO context