Early Access Docs

Introduction to RevEngine

RevEngine gives insurance brokers a live intelligence layer over their entire policy portfolio — tracking coverage gaps, renewal risk, churn signals, and cross-sell opportunities across every carrier and line of business.

How RevEngine works

RevEngine connects to your carrier data sources and runs a three-step process to build and maintain your policy portfolio intelligence layer.

        // RevEngine data flow

        ingest   → Policy data in from CSV, GoHighLevel, AMS, or carrier feeds

        enrich   → Policyholders matched, coverage scored, renewal dates indexed

        surface  → Opportunities, risks, and scores delivered to the app + API

💡 RevEngine normalizes data from every carrier into a single policyholder view — no manual reconciliation across spreadsheets or agency management systems.

Quick start

Get your first carrier export into RevEngine and see your portfolio intelligence in under 10 minutes.

Create your RevEngine account — Sign up via early access. You'll receive credentials for your admin dashboard and API access.

Upload your first carrier export — Use CSV import to load a policy roster. Map the carrier, effective dates, and coverage fields. RevEngine normalizes it into your portfolio automatically.

Configure your carriers and coverage scenarios — Define the carriers you work with and the cross-sell scenarios you want RevEngine to evaluate (e.g., "Has Medicare → No Life"). RevEngine scores every policyholder against them.

Review your portfolio dashboard — Open the Cross-Sell Finder, Coverage Map, and Scorecards views. Your first set of opportunities and risk signals will be surfaced automatically based on your uploaded data.

Connect a live data source — Link GoHighLevel, AgencyZoom, or another AMS to keep your portfolio intelligence up to date automatically. See the Integrations section for platform-specific setup guides.

Key concepts

Policyholders

The core entity in RevEngine. A policyholder is a client with one or more active policies across any number of carriers and lines of business. RevEngine builds a unified record per policyholder — deduplicating across data sources and tracking their full coverage history over time.

Policies

A single coverage contract. Each policy has a carrier, line of business, effective date, premium, and status. Policies are the raw data RevEngine ingests — from CSV uploads, AMS integrations, or direct carrier feeds — and the foundation of all portfolio analysis.

Coverage Scenarios

A configurable rule that defines a cross-sell or gap-fill opportunity. For example: "policyholder has Medicare but no Life or Annuity product." RevEngine evaluates every policyholder against your configured scenarios and surfaces matches as actionable opportunities in the dashboard and API.

Scorecards

A per-agent or per-team summary of portfolio health: total policies, retention rate, open opportunity count, carrier concentration, and penetration rate. Scorecards update automatically as the underlying portfolio data changes.

Carriers

The insurance companies whose policies appear in your portfolio. Each carrier is configured in RevEngine with its line mappings and data format details, allowing RevEngine to normalize coverage data across your entire book into a consistent structure.

Exceptions

A record that RevEngine could not enrich automatically — due to missing policyholder matching data, an unrecognized carrier, or a malformed import. Exceptions are surfaced in the dashboard and must be resolved before the affected records are included in portfolio analysis.

API overview

The RevEngine REST API gives you programmatic access to your policy portfolio: policyholder records, coverage gaps, opportunity signals, and agent scorecards. Full API reference documentation is coming soon — available to early access partners on request.

⚠️ The RevEngine API is currently in early access. Endpoints and field names are subject to change. We'll notify all API users before making breaking changes.

Authentication

All API requests are authenticated using an API key sent in the request header:

        GET https://api.revengine.app/v1/policyholders

        Authorization: Bearer re_live_xxxxxxxxxxxx

        Content-Type: application/json

Core endpoints

Endpoint	Method	Description	Status
/v1/policyholders	GET	List all policyholders with coverage summary	Available
/v1/policyholders/:id	GET	Get full coverage history for a policyholder	Available
/v1/opportunities	GET	List open coverage gaps and cross-sell signals	Available
/v1/scorecards	GET	Get agent scorecards for current period	Coming soon
/v1/carriers	GET	List configured carriers and line mappings	Coming soon
/v1/webhooks	POST	Register a webhook for opportunity or renewal events	Coming soon

MCP Access

RevEngine exposes a Model Context Protocol (MCP) server that gives any MCP-compatible AI agent — Claude, Cursor, or your own — live read access to your policy portfolio: policyholder records, coverage gaps, renewal timelines, and opportunity signals.

What you can do with the MCP

Ask natural language questions about your book of business
Pull coverage gap lists directly into Claude or Cursor
Automate outreach triggers by querying renewal risk scores
Build custom AI workflows on top of live portfolio data

Quick setup

Add the following to your Claude Desktop or Cursor MCP settings file, then restart the application:

        // claude_desktop_config.json or cursor mcp.json

        {

          "mcpServers": {

            "revengine": {

              "command": "npx",

              "args": ["-y", "@revengine/mcp"],

              "env": {

                "REVENGINE_API_KEY": "re_live_xxxxxxxxxxxx"

              }

            }

          }

        }

Your API key is in Settings → API Keys inside your RevEngine dashboard. MCP access is available to all early access users at no additional cost.

🔒 The RevEngine MCP server provides read-only access to your portfolio data. Queries run against the RevEngine API using your key — no data is stored by or transmitted through the MCP server itself.

Quick Start →