This is a preview version of the API intended for early testing and integration. Preview versions are not stable and may include breaking changes before general availability.

Metric catalogue

Two metrics today. Each name is a contract: its version moves only when its meaning does, and a changed meaning ships as a new version with a deprecation window. Each metric's findings has its own shape; the fields are summarised here and listed in full on POST /intelligence/metrics.

Shares are fractions (0.3107 is 31 %). Every field in findings may be null, and a null field is left out of the response rather than sent as null: a cover whose holding is unknown has no held, and a cover without a share has no peerShare. Treat a missing field as null. A missing list is not an empty one.

Insurance

insurance.coverage_held

  • What which covers each car, condo and villa policy holds, and next to each cover the share of comparable Swedish policies holding it
  • Version 2
  • Reads the insurance line: car, condo and villa policies
  • Fields in findings: peerCountRequired, peerDataAvailable, benchmarkSnapshotDate, policyLevel[], benchmarks
  • Compared with policies in the same policy group and age band

Per policy (policyLevel[], with collectionId and productId): the policyGroup its covers are read in (car_full, car_half, car_traffic, car_laid_up, condo, villa_contents, villa_house_only), whether its covers matched the insurer's package catalogue (coverageMatched), and the peer comparison (peerGroup, peerPolicyCount, peerStatus: compared, or why not). Per cover: parameterName, group, held (a null held is unknown, not false), kind (package or add_on) and peerShare. benchmarks is not filled by this route.

peerStatusMeaning
comparedcompared with its peer group
group_unknownthe covers that decide a car's or villa's group aren't known, usually because the policy didn't match the insurer's package catalogue; it has no peers even when the age is known
group_not_comparedlaid-up and traffic-only cars, house-only villas: covers without shares
no_segmentno age
no_snapshotno peer data loaded
group_below_floorfewer than peerCountRequired policies in the peer group
not_scoredoutside Sweden

Reading insurance.coverage_held:

  • Which covers are listed. Each policy group has a fixed set of covers, the same for every policy in the group, whatever else the policy holds; a car or villa without a group lists the full-cover car's or the villa-with-contents' set. The covers that decide the group aren't listed, nor is a cover that almost every policy of the group held, or almost none, when the sets were chosen.
  • Why a peerShare is null. Either the policy isn't compared, and its peerStatus says why, or the policy is compared but fewer than 200 comparable policies have a known answer for that cover. Branch on peerStatus, not on a null peerShare. A condo always has its group, so a condo that didn't match the catalogue is still compared, with every held null.
  • Half cover isn't a gap. A car's cover level only picks its peer group: half-cover cars are compared with other half-cover cars, and vehicle damage itself isn't listed. Many newer Swedish cars carry the manufacturer's vehicle damage guarantee (vagnskadegaranti) for their first years, and the metric doesn't know the car's age, so half cover doesn't mean vehicle damage is uncovered.
  • Comparable policies, not people like you. The shares mostly reflect which packages the insurers sell: which insurer people chose explains more of the differences than their age.

Against the insurance data API. Both start from the same cover value per policy: the value of each coverage parameter in the insurance data API. The metric doesn't change that value, it only turns it into held, and where the value leaves it open whether a cover is held, held is null rather than a guess:

Insurance data API valueheld here
true: included, or an add-on that was bought (isAddonPurchased)true
false: not includedfalse
add-on: offered as an add-on, no purchase recordedfalse where the insurer's data records purchases of that cover; otherwise null, since it may have been bought
possible: can't be determinednull

Two more differences: the metric lists only the policy group's set of covers, not every cover the policy has; and a cover that appears twice for one policy is listed once, held if either entry holds it.

Wealth

wealth.concentration

  • What how concentrated the wealth holdings are
  • Version 4
  • Reads the wealth line; over a USER source only for a client on the wealth product line (asked for by name it answers 400, left to the default it is left out)
  • Fields in findings: version, holdingsCountRequired, benchmarkSnapshotDate, fxRatesAvailable, fxAsOf, input, userLevel, productLevel[], peerDataAvailable
  • Compared with people in Sweden in the same age band and the same population (scope: investments, pension or combined); a peer group is published only with at least 200 people in it

It reports what was computed with (version, holdingsCountRequired, benchmarkSnapshotDate, FX availability, the input tallies), the measures at user level (scope, holdings count, hhi from 0 to 1, effectiveHoldingsCount, largestPositionPct, the largest positions, top3Pct) and per product, and, when the person's age is known, a peer block: the cohort (country and age band, for example SE_45_59), its size, the person's percentiles and the peer medians with percentile ladders (p10 to p90 for hhi, narrower for the other measures).

Reading wealth.concentration:

  • Holdings without a currency can't be valued, so they are left out and counted in holdingsExcludedNoFx. This is not common: today one pension provider reports no currency for its holdings, for every pension it holds. Such a pension adds no positions, and a person whose only holdings are of this kind gets no measures (holdingsCount 0, holdingsCountSufficient false).
  • Identifiers that aren't ISINs. The isin field, in largestPositions[] too, can hold another identifier, such as a fund-data id (0P…) that a pension provider sends in place of the ISIN. This is not common: one provider today. Positions are told apart by this field, so a fund one provider reports by such an id and another by its ISIN counts as two positions, and the person looks more spread out than they are. A portfolio a provider reports under one code counts as one position, as a fund does; also not common, one provider today. A holding with no identifier is left out and counted in holdingsExcludedNoIsin.