> 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-journeys/readme.md).

# Product Overview

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

XCover Journeys (XCJ) is a Cover Genius-hosted insurance purchase experience that partners embed in their websites or mobile apps. Cover Genius owns the page, layout, flow, payment, and booking. No frontend code to build, deploy, or maintain.

{% hint style="info" %}
If you already use the XCover API, XCJ complements it. XCJ handles the insurance purchase journey; the XCover API continues to handle booking management, cancellations, and other policy lifecycle operations.
{% endhint %}

### How it works

Cover Genius hosts each journey at a URL unique to your integration. You embed this URL in your platform — as an **iframe** on web or in a **WebView** on mobile. Both methods use the same journey URL. No SDKs or client-side libraries are required.

The journey guides customers through product selection, personal details, pricing, payment, and confirmation — all without leaving your site.

#### Journey flow

The exact steps vary by partner and product, but a typical journey follows this sequence:

```
Customer Details  →  Offers  →  Quote Estimate  →  Payment  →  Confirmation
```

1. **Customer Details** — Customer provides or confirms personal information and details relevant to their coverage.
2. **Offers** — Customer reviews coverage options and selects a product.
3. **Quote Estimate** — Customer reviews premium breakdown, taxes, and total.
4. **Payment** — Customer enters payment details. Payment is managed entirely by Cover Genius.
5. **Confirmation** — Booking is confirmed. Customer sees a summary with next steps.

### What Cover Genius manages

* **Payment processing** — Payments are handled within the journey. Partners do not interact with payment infrastructure directly.
* **Experimentation** — A/B testing is built in. Cover Genius runs experiments on content, layout, and flow to optimize conversion — no partner involvement required.
* **Content management** — All UI copy (labels, messages, disclaimers) is managed by Cover Genius and can be updated without a code release.
* **Monitoring** — Cover Genius monitors journey health, error rates, and performance.


---

# 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-journeys/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.