Noetis Insurance · Business engine

Commercial Insurance Policy Comparison API

Compares commercial policy wording with supplied coverage requirements.

Answers: "Can an engine compare policy wording against our coverage needs?" For risk managers and brokers.

Not insurance advice. Coverage decisions belong to a qualified broker or adviser.

Configure in Studio Request an evaluation Test engine (sign in)

Available today

Implemented

Implemented: runs on the shared runtime with supplied material. One bounded development check on 2026-10-12 took 109.9s with 13 model calls and ended "incomplete". That is a development signal, not an evaluation. Customer access is by approved account.

What you send

Question
Supplied text material
Text material up to 150,000 characters per run

What comes back

Policy comparison with exact wording references.
Findings with the located quote and a support status from claim review
Release status: released, incomplete with reasons, or failed
Executed roles, usage and measured cost

Sample

Authored illustration. Written by Encevra to show the workflow. Not customer data and not a recorded model output.

Compare these two liability policies for our café.

Policy A: limit $1M per occurrence, $2M aggregate, deductible $1,000, excludes liquor liability. Policy B: limit $2M per occurrence, aggregate not stated, deductible $2,500, liquor liability included up to $500k. We serve wine in the evenings.

The real response shape is documented in the API reference.

How the workflow operates

Each role is a responsibility in the workflow, served by a third party language model. More roles are not automatically better; depth and routing decide which run.

Built with

Models this engine uses: OpenAI (GPT), Anthropic (Claude). Specialists run on OpenAI models and the claim review and final brief on Anthropic models. If a provider has a temporary failure, the step can fall back to an OpenAI model, and the run records that.

Policy Mapper

Extract coverage sections and definitions.

Limits Analyst

Normalize limits, deductibles and sublimits.

Exclusions Reviewer

Identify exclusions and endorsement interactions.

Requirements Analyst

Map wording against stated needs.

Ambiguity Reviewer

Identify unclear terms and questions for a qualified reviewer.

Evidence and deployment

Evidence

This engine reads the text you send in the request. Each released finding carries the exact quote and its character span in that text, located mechanically before release. Quotes that cannot be located are labelled Insufficient evidence and never shown as source verified. Interpretation is reviewed as a separate step, and gaps such as a missing clause describe what was searched instead of citing text that is not there.

Deployment

Runs on Encevra hosted infrastructure using the third party models listed above. Every model call and fallback is checked against the deployment policy first. Private cloud and air-gapped deployment are planned; discuss deployment requirements.

What it does not handle

Binding coverage determinations
Automated claim denial
Uses only supplied material. No freshness guarantee beyond the documents provided.
Required for every output during trials.

How to integrate

Send "engine": "insurance" with your question and material from your server. Keys stay server side.

How to evaluate it

No published result for this workflow yet. Build a small answer key from your own work and compare against a strong single model baseline. See the evaluation checklist and method.

Cost and rights: pricing and licensing. Showing outputs to your own customers needs a written agreement.

Schedule an engine setup call

Related engines

Content reviewed 2026-10-12 by the Encevra engine team. Engine version 0.1.0 on noetis-core-1.