> For the complete documentation index, see [llms.txt](https://partner-docs.covergenius.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://partner-docs.covergenius.com/xcover-elements/readme.md).

# Product Overview

This document outlines the integration requirements for a partner to use XCover Elements (XCE), serving as a comprehensive yet concise reference, it is designed to complement a partner-specific guide.

## Background

The current integration between Partners and XCover requires Partners to create and maintain the XCover protection panel's user interface (UI). XCE addresses these challenges and offers the following key benefits:

### Seamless Integration

XCE provides a minimal integration solution that seamlessly delivers the XCover protection panel to customers on the Partner platform via our Content Delivery Network(CDN).

### Streamlined AB Testing

XCE empowers CG Growth Product Managers (GPM) to conduct AB testing with minimal to no reliance on Partners, fostering experimentation and optimization. Partner is involved from a strategic point of view, understanding what experiments CG wants to run but not having to create them.

### Rapid Updates

XCE enables the continuous release of new features and updates to our protection panel without requiring technical support from Partners.

{% hint style="info" %}
XCE scripts use semantic versioning. Any major version release will be done together with Partner to adjust any potential integration breaking changes.
{% endhint %}

### Future Proof

XCE is future proof whereby new features we develop in the future for Partners can be seamlessly deployed with zero or minimal technical involvement from them.

{% hint style="warning" %}
XCE is designed to complement Cover Genius's existing XCover integration and does not replace it.
{% endhint %}

### Confirm Offer integration

XCover Elements handles the offer presentation to the customer. Once the customer has selected our protection product(s) the partner needs to handle confirm offer and other related booking management functions.

This process is documented under [API Integration](/xcover-elements/api-integration/summary.md).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://partner-docs.covergenius.com/xcover-elements/readme.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.