Skip to main content
Rules applied to all coverages:
  1. If both the limitPerAccident and limitPerPerson values are provided for a coverage, the limitPerAccident value must be greater than the limitPerPerson value.
  2. If a specified coverage is afforded to all properties on the policy, the property field will be undefined.
For standardization purposes, Axle performs opinionated data transformation of insurance carriers’ data into the Axle Schema. As a result, Axle makes certain carrier enumeration inferences to map carrier data into the Axle Schema.

Auto Policy Coverage Types

Rules applied:
  1. If the carrier returns limits combined as “$50,000 / $100,000”, the first value represents limitPerPerson and the second value represents limitPerAccident. If there is only a single limit returned, the limit will be recorded as limitPerAccident.
  2. If the policy returns a combined single limit (CSL) for Bodily Injury and Property Damage, the limit will be set as limitPerAccident for both Bodily Injury and Property Damage coverages.
Suppression checks:
  1. limitPerAccident, limitPerPerson, and deductible fields contain certain min / max value thresholds used to suppress inaccurate or nonsensical data.

Fields

code
string
required
BI
label
string
required
Bodily Injury
limitPerAccident
number or null
limitPerPerson
number or null (optional)
Rules applied:
  1. If the carrier returns limits combined as “$50,000 / $500”, the first value represents limitPerAccident and the second value represents the deductible.
  2. If the policy returns a combined single limit (CSL) for Bodily Injury and Property Damage, the limit will be set as limitPerAccident for both Bodily Injury and Property Damage coverages.
Suppression checks:
  1. limitPerAccident and deductible fields contain certain min / max value thresholds used to suppress inaccurate or nonsensical data.

Fields

code
string
required
PD
label
string
required
Property Damage
limitPerAccident
number or null
deductible
number or null (optional)
Rules applied:
  1. If the carrier returns limits combined as “$50,000 / $100,000”, the first value represents limitPerPerson and the second value represents limitPerAccident. If there is only a single limit returned, the limit will be recorded as limitPerAccident.
  2. If the policy returns a combined single limit (CSL) for Uninsured Motorists Bodily Injury and Uninsured Motorists Property Damage, the limit will be set as limitPerAccident for both Uninsured Motorists Bodily Injury and Uninsured Motorists Property Damage coverages and limitPerPerson will be undefined.
Suppression checks:
  1. limitPerAccident and limitPerPerson fields contain certain min / max value thresholds used to suppress inaccurate or nonsensical data.

Fields

code
string
required
UMBI
label
string
required
Uninsured Motorists Bodily Injury
limitPerAccident
number or null
required
limitPerPerson
number or null (optional)
Rules applied:
  1. If the carrier returns limits combined as “$50,000 / $500”, the first value represents limitPerAccident and the second value represents the deductible.
  2. If the policy returns a combined single limit (CSL) for Uninsured Motorists Bodily Injury and Uninsured Motorists Property Damage, the limit will be set as limitPerAccident for both Uninsured Motorists Bodily Injury and Uninsured Motorists Property Damage coverages and limitPerPerson will be undefined.
Suppression checks:
  1. limitPerAccident and deductible fields contain certain min / max value thresholds used to suppress inaccurate or nonsensical data.

Fields

code
string
required
UMPD
label
string
required
Uninsured Motorists Property Damage
limitPerAccident
number or null
deductible
number or null (optional)
Rules applied:
  1. If the carrier returns limits combined as “$50,000 / $100,000”, the first value represents limitPerPerson and the second value represents limitPerAccident. If there is only a single limit returned, the limit will be recorded as limitPerAccident.
Suppression checks:
  1. limitPerAccident and limitPerPerson fields contain certain min / max value thresholds used to suppress inaccurate or nonsensical data.

Fields

code
string
required
UIMBI
label
string
required
Underinsured Motorists Bodily Injury
limitPerAccident
number or null
required
limitPerPerson
number or null (optional)
Rules applied:
  1. If the carrier returns limits combined as “$50,000 / $500”, the first value represents limitPerAccident and the second value represents the deductible.
Suppression checks:
  1. limitPerAccident and deductible fields contain certain min / max value thresholds used to suppress inaccurate or nonsensical data.

Fields

code
string
required
UIMPD
label
string
required
Underinsured Motorists Property Damage
limitPerAccident
number or null
deductible
number or null (optional)
Rules applied:
  1. If the carrier returns limits combined as “$50,000 / $100,000”, the first value represents limitPerPerson and the second value represents limitPerAccident. If there is only a single limit returned, the limit will be recorded as limitPerAccident.
Suppression checks:
  1. limitPerAccident and limitPerPerson fields contain certain min / max value thresholds used to suppress inaccurate or nonsensical data.

Fields

code
string
required
UUIMBI
label
string
required
Uninsured & Underinsured Motorists Bodily Injury
limitPerAccident
number or null
required
limitPerPerson
number or null (optional)
Rules applied:
  1. If the carrier returns limits combined as “$50,000 / $500”, the first value represents limitPerAccident and the second value represents the deductible.
Suppression checks:
  1. limitPerAccident and deductible fields contain certain min / max value thresholds used to suppress inaccurate or nonsensical data.

Fields

code
string
required
UUIMPD
label
string
required
Uninsured & Underinsured Motorists Property Damage
limitPerAccident
number or null
deductible
number or null (optional)
Suppression checks:
  1. limitPerAccident and deductible fields contain certain min / max value thresholds used to suppress inaccurate or nonsensical data.

Fields

code
string
required
COLL
label
string
required
Collision
limitPerAccident
number or null (optional)
deductible
number or null
property
string or null
Suppression checks:
  1. limitPerAccident and deductible fields contain certain min / max value thresholds used to suppress inaccurate or nonsensical data.

Fields

code
string
required
COMP
label
string
required
Comprehensive
limitPerAccident
number or null (optional)
deductible
number or null
property
string or null

Home/Condo/Renters Policy Coverage Types

Rules applied:
  1. When the deductible is listed differently based on the type of claim, the deductible associated with covered perils will be returned. This deductible value is often represented as “All Perils”, “All Covered Perils”, or “Other Covered Perils”.
Suppression checks:
  1. If both the policy premium and Dwelling coverage limitPerAccident values are defined, the Axle Service will ensure that the premium-to-Dwelling-limitPerAccident ratio falls within our set bounds of reasonability. If this ratio is greater than our upper bound, both the policy premium and Dwelling coverage limitPerAccident values will be conservatively set to null. If a premium value exists but no Dwelling limitPerAccident value is present, then the premium will be conservatively set to null.
  2. limitPerAccident and deductible fields contain certain min / max value thresholds used to suppress inaccurate or nonsensical data.

Fields

code
string
required
DW
label
string
required
Dwelling
limitPerAccident
number or null
deductible
number or null
Rules applied:
  1. When the deductible is listed differently based on the type of claim, the deductible associated with covered perils will be returned. This deductible value is often represented as “All Perils”, “All Covered Perils”, or “Other Covered Perils”.
Suppression checks:
  1. limitPerAccident and deductible fields contain certain min / max value thresholds used to suppress inaccurate or nonsensical data.

Fields

code
string
required
OS
label
string
required
Other Structures
limitPerAccident
number or null
deductible
number or null
Rules applied:
  1. When the deductible is listed differently based on the type of claim, the deductible associated with covered perils will be returned. This deductible value is often represented as “All Perils”, “All Covered Perils”, or “Other Covered Perils”.
Suppression checks:
  1. limitPerAccident and deductible fields contain certain min / max value thresholds used to suppress inaccurate or nonsensical data.

Fields

code
string
required
PP
label
string
required
Personal Property
limitPerAccident
number or null
deductible
number or null
Rules applied:
  1. When the deductible is listed differently based on the type of claim, the deductible associated with covered perils will be returned. This deductible value is often represented as “All Perils”, “All Covered Perils”, or “Other Covered Perils”.
Suppression checks:
  1. limitPerAccident and deductible fields contain certain min / max value thresholds used to suppress inaccurate or nonsensical data.

Fields

code
string
required
LOU
label
string
required
Loss of Use
limitPerAccident
number or null
deductible
number or null (optional)
Suppression checks:
  1. limitPerAccident and deductible fields contain certain min / max value thresholds used to suppress inaccurate or nonsensical data.

Fields

code
string
required
PL
label
string
required
Personal Liability
limitPerAccident
number or null
Rules applied:
  1. Only a limitPerAccident or limitPerPerson value can exist on this coverage but not both.
Suppression checks:
  1. limitPerAccident and deductible fields contain certain min / max value thresholds used to suppress inaccurate or nonsensical data.

Fields

code
string
required
MED
label
string
required
Medical Expenses
limitPerAccident
number
limitPerPerson
number

Flood Policy Coverage Types

Suppression checks:
  1. limitPerAccident and deductible fields contain certain min / max value thresholds used to suppress inaccurate or nonsensical data.

Fields

code
string
required
DW
label
string
required
Dwelling
limitPerAccident
number or null
deductible
number or null
Suppression checks:
  1. limitPerAccident and deductible fields contain certain min / max value thresholds used to suppress inaccurate or nonsensical data.

Fields

code
string
required
PP
label
string
required
Personal Property
limitPerAccident
number or null
deductible
number or null
I