AI Data · Maximum Insurance

Travel insurance and traveller safety cases, with the right answer and an automatic grader

To train and evaluate your AI models on the decisions a travel insurer makes: which risk level to retain for a stay, what a policy covers when an incident happens, what the traveller is left to pay.

For insurtech and AI start-ups, university labs and data brokers.

  • Cases shown are checked automatically
  • 16 points checked by a program, not by an AI

One case, in short

The question

“An employee leaves on a ten-day business trip. Which risk level should be retained for this stay?”

In the sources

France: increased vigilance, level 2 of 4 (source S1). United Kingdom: no specific advice, level 1 of 4 (source S2).

The right answer

Level 2 of 4: retain the most cautious of the ministries read, citing each one.

A wrong answer, for comparison

Level 1 of 4: keeping the most reassuring advice.

The grader's verdict

FAIL M1 Retained level by precaution

One of the checks that apply to this case fails: the answer is refused, with no human judge.

Simplified example. A real case has up to 15 dated sources: try one below.
The problem

Why do models need these cases?

To know whether an AI model makes a travel insurer's decisions correctly, and to train it to make them, you need examples whose right answer is known, and that a program can check on its own, without human review. That is what we provide.

What our checks verify, for instance

  • The travel advice retained is the most cautious of the ministries read, not the most reassuring.
  • The right policy line is read for the incident: covered, or not.
  • The cap and the deductible are applied when computing what is left to pay.
  • Every cited source says what is claimed, and every figure is found in it.
What you buy

What exactly are you buying?

Complete cases, ready to use. Each one brings together four things, like the example at the top of the page.

Every source

Up to 15 dated sources per case: official alerts (GDACS), the advice of 5 foreign ministries, policy notices. The stay may be simulated; the sources are real.

The right answer

A reference answer assembled by a program from the case's verified elements. Each case is checked automatically: quality control (brief generated without error) and grader; the checked share is shown for each dataset.

A wrong answer to avoid

When there is one, a typical wrong answer: a real discarded draft, or a mistake introduced on purpose and labelled as such.

An automatic grader

A program that checks up to 16 precise points (cited sources, numbers, dates, risk level, policy lines, amount left to pay) and says in under a second how many are right, among those that apply to the case.

For technical teams: the 16 checks, one by one

Binary outcome, pass or fail, no LLM judge: numeric equalities, set membership, verbatim quotes, recomputation. No check looks for a keyword. A missing required field fails; an unreadable answer fails every check. A check may not apply to a case (“not applicable”, stated by the right answer): our pages and cards then read the score on the checks that apply only, whereas the shipped grader's total out of 16 counts it as passed. Eight checks are common to every dataset (C1 to C8), eight are specific to travel insurance (M1 to M8).

CheckWhat is verifiedRight answer read from
C1
Answer matches the schema
JSON that matches the enforced answer schema: types, enums, required fields, no extra property.the domain schema (answer_schema)
C2
Citations resolve
Every cited source exists in the context; a factual claim without a citation fails.grounded_context.sources[].id
C3
Verbatim quotes
Every quote of at least 12 characters is found in the cited source (case, accents and spaces normalised).sources[].content_norm
C4
Numbers traceable
Every number in a factual claim appears in the cited source (±0.5%, k / M / bn / % units).the cited sources
C5
Dates consistent
No date after the reference date, except those the context already carries; event dates are in the source.as_of, sources[].published
C6
Arithmetic consistent
Low ≤ mid ≤ high; a total equals the sum of its parts; a percentage stays between 0 and 100.the answer itself
C7
No internal contradiction
A contract judged “assez” (sufficient) has no blocking line left uncovered (on the Proplace side: a fatal deal killer forbids a favourable verdict).the domain rule
C8
Honest abstention
What cannot be computed is null with a reason; what can be computed carries a value; blanket abstention fails.non_computable[] in the ground truth
M1
Retained level by precaution
The retained level is the most cautious of the ministries read, and “divergent” follows Maximum's rule.conflict_resolution_record
M2
Level per ministry
The level of each of the 5 ministries (US, FR, GB, CH, CA) as it was read; a ministry not read stays null, inventing one fails.readings[]
M3
Required lines of the stay
Every line of needs is classed blocking / useful / not applicable as in the ground truth.gap.lines[].required
M4
Contract line status
The status of the blocking lines (couvert, sous_conditions, non_couvert, non_documente, sans_objet) for the stay's contract and the contracts of the remaining-cost table.market matrix: contracts[pid].lines[cid].status
M5
Contract verdict
assez / a_completer / inconnu, contract by contract.matrix.contracts[pid].verdict
M6
Remaining cost recomputed
Remaining cost = cost − max(0, min(cost, cap) − deductible), within ±1 €, in EUR; unlimited cap: only the deductible is left to pay; benefit not covered or excluded by the stay: the whole cost; null only when it cannot be computed.quantum.scenarios[].columns[] (soins, evacuation, extraction, interruption)
M7
Counts per radius
UCDP events within 5, 20, 50 km, storms within 500 km, nearest hospital within ±1 km.stay_second_order_checks.from_hotel
M8
Formality deadlines
Filing deadline (apply_by) and overdue flag per formality.formalities[] and rules_check
What it is for

What will these cases do for you?

Measure

See, point by point, what your model gets right and what it misses.

Train

Reward it when the grader accepts its answer, and show it the right and the wrong answer side by side.

Prove

Compare two versions of your model on the same cases, with the same grid.

The proof

How many checks do current models pass?

For each market model: the share of checks passed among those that apply to each case, as a median over the dataset's cases. Not-applicable checks do not count. Unaided, at temperature 0: the same question always gets the same answer. A perfect answer scores 100%.

not measured

The measurement in detail, check by check

Every version of a dataset publishes its measurement: market models, temperature 0, one stored and fingerprinted answer per case and per model, scored by the same grader. The figures are read from the API when the page loads, never written here; without a published measurement, the page says “not measured”.

not measured

Try it now

Does your model find the right answer?

Pick an automatically checked case, copy the question and its sources into your model, then paste its answer: the grader says how many of the checks that apply to this case it passes, point by point. The right answer is not shown, so nothing is hinted to your model: it is in the free sample.

1 The case

The question as posed to the model, then its sources. The “Copy” button takes the question, the sources and the answer format: never the right answer.

Loading public cases…

2 Your model's answer

Give the question and its sources to your model, paste its answer here, then run the 16 checks. Only the score is logged, never the text.

The 16 checks of this case
    For technical teams: load the dataset in three lines
    Import snippet read from the buyer profile served by the API…

    The grader shipped in the dataset is this page's grader: your own answers are scored on the same grid, offline, with no dependency.

    What you get

    What is in each dataset?

    mi-arbitration

    Coverage arbitration cases

    A simulated stay, a real incident reported near the hotel, the real advice of 5 ministries and the policy notices. The question: which risk level to retain, which policy lines cover, what is left to pay.

    Number of cases
    read on load
    Version
    version not read
    Checked automatically
    read on load
    Updates
    through new numbered versions; a delivered version never changes
    Format
    JSON Lines, descriptive card, Python grader
    Licence
    standard non-exclusive; exclusivity available on request

    mi-duty-brief

    Trip briefs (duty of care)

    The document that prepares a business trip: country risks, formalities, what the policy covers. Every brief comes from a stay entered in Maximum's software, with its dated sources; the traveller's name is removed.

    Number of cases
    read on load
    Version
    version not read
    Checked automatically
    read on load
    Updates
    through new numbered versions; a delivered version never changes
    Format
    JSON Lines, descriptive card, Python grader
    Licence
    standard non-exclusive; exclusivity available on request

    Data platforms and brokers: the standard licence is non-exclusive, and every dataset ships with its descriptive card (content, provenance, source licences). Redistribution is agreed case by case.

    For technical teams: the format of a row

    A JSON Lines file (one case per line), with its descriptive card (DATA_CARD.md), its Croissant metadata (croissant.json) and the grader in Python. Each row carries:

    • prompt — the system prompt and the case, as given to the model.
    • grounded_context — the reference date, the language, at most 15 sources of 4,000 characters (id, title, URL, date, kind, content, normalised content, numbers, sha256), the facts and the stated rules.
    • answer_schema — the JSON schema enforced on the answer, with no additional property.
    • checks — the 16 checks and, for each, whether it applies (declared by the ground truth).
    • ground_truth — the ground truth, opaque in the prompt: it only serves the grader.
    • chosen — the reference answer, which passes every check that applies, with its grading grid.
    • rejected — when it exists, a rejected answer: a real draft or a labelled deterministic perturbation (rules R1 to R10, seed derived from the id); the DATA_CARD publishes the share of each.
    • baseline — the score of each market model on this case, when measured.
    • provenance — origin (real sidecar or simulated stay), origin reference and hash, generator versions, anonymisation profile, validation (automatic check; optional review).
    • licence — the licence name, its URL, the exclusivity and the row's upstream attributions.
    The licence in detail
    • Sample: evaluation licence AIDATA-EVAL-v1, 90 days, internal use (LICENSE.md in the archive).
    • Purchase: standard non-exclusive licence (AIDATA-STD-v1), or exclusivity in your sector (AIDATA-EXCL-v1).
    • The sources come from Maximum's engine: GDACS feeds, GeoNames cities, UCDP events, NOAA storms, the advice of the 5 foreign ministries (US, FR, GB, CH, CA), the hospital network, policy notices read by Maximum (short, dated quotes); for briefs, the companion files of generated briefs. Their licences (UCDP and GeoNames CC BY 4.0, FCDO Open Government Licence v3, Canada Open Government Licence, State Department public domain, GDACS terms to confirm) are listed in the DATA_CARD and in croissant.json.

    The full licence terms

    The offers

    How do you get them?

    The example case is free; custom work is quoted, excluding taxes.

    One example case, free

    To judge for yourself, before any order.

    $0no account
    • The most recent automatically checked case: the question, its dated sources and the answer format
    • The online grader: paste your model's answer, it says point by point what is right
    • The right answer and the grader to run on your side, in the free sample, under the evaluation licence AIDATA-EVAL-v1, 90 days
    Try the example case

    Available as soon as cases have been checked automatically (quality control and grader): no sample is offered before then.

    Custom

    For a specific volume, pace or exclusivity.

    custom quoteproduced for you after the order
    • From 150 cases, produced after your order, within the lead time written in the quote
    • Every delivered case checked automatically: quality control and grader
    • A contract or your purchase order, then an invoice payable by SEPA transfer
    • Non-exclusive licence, or exclusivity in your sector
    Let's talk about your custom need
    Request a quote

    Describe your needs.

    Three choices and an email address are enough. We answer with a quote (price and production lead time), then a contract or your purchase order. The cases are produced for you, checked automatically (quality control and grader), then delivered with the invoice.

    • Volume: from 150 cases
    • Pace: in one batch, or every week
    • Licence: non-exclusive, or exclusive in your sector

    Or write to us: contact@maximum-insurance.com. The page only shows your request's reference, no contact detail.

    Frequently asked questions

    Before you buy.

    The licence terms prevail.

    Licence terms
    How are the cases made? Did an AI write the texts?

    Partly, and we say so. Trip briefs are written by Maximum's engine, which relies on commercial AI models; each version's descriptive card says which ones. The right answer of each case, however, is not written by an AI: a program assembles it from the case's verified elements (levels read from each ministry, policy lines, recomputed amounts). Each case is then checked automatically: quality control (brief generated without error) and grader; the checked share is shown for each dataset. The grader is a program, with no AI judge.

    What is real, and what is simulated?

    Arbitration cases start from simulated stays: the traveller and the stay are generated by a program. What they meet is real and dated: the advice of foreign ministries, GDACS alerts, UCDP events, NOAA storms and the policy clauses read by Maximum. Briefs come from stays entered in Maximum's software, on client, demo and test accounts: each dataset's card gives the breakdown.

    What is removed from the data?

    The traveller's name, emails and phone numbers are replaced by tokens; the identifiers of the people who validated a brief are never copied; a case where a trace remains is discarded. Hotel, dates, age, nationality and activity are kept: they are the substance of the decision. Details are in our privacy policy.

    How are the cases checked, and how can I tell?

    Automatically, case by case: the quality control checks that the brief was generated without error, then the grader checks that the reference answer passes every check that applies to the case. A case that fails is neither shown nor sold. A human review remains possible, and optional: it can discard a case. This page only shows validated cases; each dataset card says how many cases are checked; a custom order is delivered fully checked. The validation status is also written in each delivered row.

    How often are the datasets updated?

    Through new numbered versions, each with its card and its measurement; a delivered version never changes. We produce a larger volume on request, after the order.

    Which licence?

    The sample: an evaluation licence, 90 days, for internal use. Custom: the standard non-exclusive licence, or exclusivity in your sector.

    In which format?

    One case per line (JSON Lines), readable by common tools (Hugging Face datasets, pandas), with the enforced answer format, the descriptive card and the grader. Training-ready exports come with the dataset.

    How does invoicing work?

    Custom: a quote, a contract or your purchase order, then an invoice payable by SEPA transfer. The example case and the sample are free.

    Who sells this data?

    Maximum Insurance produces the cases. Proplace operates this offer for Maximum and for its own site: public cases, tester, sample, quotes and payments go through its API. The for and lead parameters of the links we send are described in the “AI Data pages” line of our privacy policy.