Data providers — Estated, Fenris, MeasureOne
Estated and Fenris provide property and risk data. MeasureOne retrieves declaration pages. Each pull consumes Data Credits.
In short: Estated for property data, Fenris for risk and additional property/auto data, MeasureOne for dec pages.
Estated — property data
Estated returns property data based on an address:
- Year built, square footage, construction type
- Owner information (where lawful and supported)
- Tax assessment data
- Recent transaction history
Used during home insurance intake to enrich the property record without asking the prospect to manually enter known facts.
Triggered when a property address is captured on a Submission and Estated is enabled on the Form.
Fenris — risk and additional data
Fenris provides:
- Property risk assessments
- Auto-related data (MVR pulls where supported)
- Additional contextual data on insureds and properties
Often used alongside Estated to build a fuller picture for underwriting.
Sample/demo data is available — you can test integrations without consuming credits. See Fenris sample data (and your integration settings) for the test path.
MeasureOne — declaration pages
MeasureOne retrieves declaration pages from prior carriers. The flow:
- The prospect provides their prior carrier and consent
- SALT calls MeasureOne to request the dec page
- MeasureOne fetches it asynchronously (this can take minutes)
- The dec page lands on the Submission as a document
A dec page request can be in one of these states on the Submission:
- Pending — request received, not yet started
- In progress — actively fetching from the carrier
- Couldn’t retrieve — carrier doesn’t support it, authentication failed, or no policy found
- Skipped — bypassed (the consumer chose not to share)
- Off — the integration is disabled
- Paused (monthly limit) — your per-vendor monthly cap has been hit
- Paused (low balance) — your Data Credit balance is too low to run the lookup
See why dec pages take a few minutes for more detail.
Per-pull costs
Each provider has a fixed per-pull credit cost:
| Provider | Cost per pull |
|---|---|
| Estated | 0.8 credits |
| Fenris | 1.6 credits |
| MeasureOne | 2.0 credits |
You can review your usage and per-vendor monthly limits in your Data Credit settings.
When pulls happen
Pulls fire when:
- A Submission completes with the relevant integration enabled
- A Form has the integration toggled on
- Sufficient data exists to run the lookup (e.g. an address for property data)
- Credit balance and per-vendor threshold allow it
Pulls do not fire on Submissions that don’t have the matching enabled integration, even if the data is captured.
Common questions
Can I use sample/demo data instead of real data for testing? Where supported (Fenris does), yes — the integration settings expose a test mode that returns canned responses without consuming credits.
Are pulls retried if they fail? Failed pulls are typically not auto-retried. The integration’s recent error log shows what failed and why. For specific Submissions, you can sometimes manually re-trigger.
Do data provider responses expire on the Submission? Once stored on the Submission, the response stays. Re-running a pull would create a new response (and consume new credits).
What’s the difference between pulling a dec page via MeasureOne vs uploading one manually? MeasureOne pulls the dec page directly from the prior carrier with the consumer’s consent — accurate, structured, automated. Manual upload is a fallback when the prospect has the file but the carrier doesn’t support MeasureOne or auth fails.