# AgenticLift product description

## Product description

[AgenticLift](/agentic-commerce/agenticlift/overview.md) is a standalone commerce engine that enables merchants to establish a fully transactional presence on GenAI channels without replatforming. It serves as a fast-deploy "agentic readiness" layer that sits on top of a merchant's existing technology stack, allowing them to turn conversational AI interfaces into revenue-generating sales channels with minimal technical risk or disruption to core systems.

As an orchestration layer, AgenticLift translates and models a merchant's product data specifically for Large Language Models (LLMs), ensuring catalogs are discoverable and comparable within AI chat experiences. This enables a complete end-to-end shopping journey where shoppers can move from initial product discovery to secure checkout directly within the AI interface.

When implementing AgenticLift, merchants gain the ability to stream real-time product information, pricing, and availability to supported AI platforms while capturing transactions through AI-enabled checkout logic. By abstracting the complexity of emerging AI protocols, AgenticLift enables enterprises to launch on new conversational channels in weeks rather than months, capturing intent and driving incremental revenue from the moment AI discovery begins.

## Defined scope

AgenticLift uses the following Composable Commerce APIs. These are a subset of the [Composable Commerce defined scope](/offering/products-overview.md), restricted to the agentic channel use case by the AgenticLift modules and contractual scope.

For notes regarding the defined scope, see [Notes to defined scope](/offering/agenticlift.md#notes-to-defined-scope).

### Notes to defined scope

- [Types](/api/projects/types.md) defines the Store and Shipping Method Custom Fields required by each module.
- [API Extensions](/api/projects/api-extensions.md) are optional and used to add custom checkout logic.
- [Subscriptions](/api/projects/subscriptions.md) are used for Order write-back to external fulfillment systems.

APIs outside this scope are not part of the AgenticLift offering. Use of APIs outside the contracted scope is subject to the governance terms described in the [implementation guide](/agentic-commerce/agenticlift/implementation.md).

## Compatibility

AgenticLift is built on [commercetools](/offering/products-overview) and inherits its compatibility model.

### commercetools APIs

commercetools uses continuous delivery to deploy updates multiple times a day. This means there are no fixed release cycles; features are released as soon as they are ready, and issues are corrected promptly.

The commercetools APIs used by AgenticLift are versionless, removing the need for version upgrades. Individual fields or actions may change as part of API evolution. These changes will not break existing solutions but might require adjustments.

If additional undocumented fields are sent in API requests, these can conflict with future new field names and cause runtime errors. Avoiding this is the responsibility of the customer.

### Platform integration specifications

AgenticLift integrates with the commerce APIs of third-party AI shopping platforms (including OpenAI and Stripe Agentic Commerce Suite) using open protocols such as the Universal Commerce Protocol (UCP). These specifications are defined, maintained, and evolved by the respective platform vendors independently of commercetools.

commercetools tracks changes to platform specifications and updates AgenticLift components accordingly. However, changes driven by third-party platform spec updates, including protocol changes, new field requirements, or shifts in integration model, are outside the standard deprecation and compatibility commitments that apply to commercetools APIs. commercetools does not control the timelines of these changes.

The availability, uptime, and behavior of the AI shopping platforms themselves are also outside the scope of AgenticLift compatibility commitments.

### SSL/TLS lifetime

To keep connections to the API secure at all times, SSL/TLS certificates are periodically renewed and replaced when adapting to newer security policies. A maximum of one certificate renewal per year is targeted. If security issues are found within encryption algorithms in use, certificates may be replaced more frequently.

## Release lifecycle

### Early access

New AgenticLift features may go through an early access phase for evaluation by selected customers. This phase aims to collect feedback early in the development cycle. Early access features should not be used in production. They do not have fully public documentation, and participants are notified of any changes directly.

commercetools may change or discontinue early access features at any time. Regardless of whether these features are free or paid, or used in test or production environments, commercetools does not offer support, service level commitments, or remedies for them.

Reach out to your commercetools contact to learn about or request access to early access features.

### Public beta

Some AgenticLift features are tagged as BETA. This means the APIs or components related to that feature can be subject to change or discontinuation:

- Breaking changes are announced three months in advance
- Removals are announced six months in advance

Announcements are made through release notes.

Public beta features are robust and secure implementations. They receive customer support and bug fixes like generally available features, but are not covered by Service Level Agreements or remedies.

### General availability

Once an AgenticLift feature is no longer in early access or tagged as BETA, it becomes generally available. The change in status is announced in release notes.

## Deprecation

As AgenticLift evolves, some features or component versions may be superseded by improved implementations. During deprecation, customers are encouraged to migrate to the updated functionality. Existing implementations continue to work during the deprecation period.

Deprecations and removals are announced in release notes. Where a deprecation is driven by a change in a third-party platform specification rather than by commercetools, the notice period may differ from the standard commercetools deprecation policy and will be communicated directly to affected customers.

## Limits

AgenticLift is subject to contractual limits in addition to the [standard commercetools API limits](/api/limits). The specific allowances and overage rates for SKU-platform units, orders, catalog syncs, and additional platform integrations are defined in your contract. Contact your commercetools representative for details.

### SKU-platform unit definition

A Product Variant in commercetools is an SKU. For the purposes of AgenticLift limits, the counted unit is the **SKU-platform unit**: one SKU synced to one AI shopping platform. Syncing the same SKU to two platforms counts as two SKU-platform units against the contracted allowance.

For example, a catalog of 30,000 product variants (SKUs) connected to two platforms (ChatGPT and Google Gemini) consumes 60,000 SKU-platform units.

The following limits apply to all AgenticLift contracts regardless of tier:

| Limit | Value |
| --- | --- |
| Full catalog syncs | Up to 1 per day |
| Price and availability updates | Up to every 15 minutes |

## Related pages

- [Area overview page with navigation](/offering.md)