> 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/client-integration/installation.md).

# Installation

This page outlines the changes that Partners will be required to make in order to integrate with XCover Elements(XCE), including all necessary changes to the existing XCover API integration.

## Via CDN

XCE is initialized by loading a Javascript module via our CDN. Add the provided script to your head tag as follows:

{% code overflow="wrap" fullWidth="false" %}

```html
// production env
<script type="module" src="https://xce.xcover.com/{partner}/{version}/xcover-elements.js" async></script>


// sandbox(test) env
<script type="module" src="https://sandbox.xce.xcover.com/{partner}/{version}/xcover-elements.js" async></script>
```

{% endcode %}

{% hint style="danger" %}
Please make sure that the script tag is present on pages where elements are expected to be used.

`{partner}` and `{version}` will be supplied by our team.
{% endhint %}

After loading the script it will automatically load our BrightWrite (BW) client side dependency via CDN. This is used to facilitate AB Testing on our panel.

## Content Security Policy (CSP)

If your site uses a CSP, add the following origins to each directive so the integration can load scripts, reach its APIs, and display assets correctly.

#### script-src:

```
xce.xcover.com
cdn.brightwrite.com
```

#### connect-src:

```
api.xone.xcover.com
relay.xcover.com
cdn.brightwrite.com
brightwrite-data.com
```

#### image-src:

```
data:
xce.xcover.com
cdn.brightwrite.com
```

{% hint style="warning" %}
**Sandbox**: If you enforce CSP in your sandbox environment, replace `xce.xcover.com` with `sandbox.xce.xcover.com` in `script-src` and `img-src`. All other origins remain the same.
{% endhint %}


---

# 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/client-integration/installation.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.