API-first integration Provides documented APIs suitable for carrier or insurtech engineering teams. | Native API-first integration: positioned as native or first‑class on fullcontact.com. Market‑map placeholder only—treat support level as unverified until researched. | Native API-first integration: positioned as native or first‑class on verisk.com. Curated seed aligned to vendor documentation; re‑validate before RFP reliance. |
ACORD integration Supports ACORD standards, messaging, mapping, or data exchange. | Unknown Founder research pending. | Unknown Founder research pending. |
Consent and permissible purpose Permissible-purpose flows, consent capture, and audit evidence by regulated use case. | Native Consent and permissible purpose: positioned as native or first‑class on fullcontact.com. Market‑map placeholder only—treat support level as unverified until researched. | Partial Consent and permissible purpose: often partial, partner‑mediated, or LOB‑specific—confirm on verisk.com. Curated seed aligned to vendor documentation; re‑validate before RFP reliance. |
Attribute lineage and metadata Field-level lineage, vintage, refresh cadence, and schema drift handling for attributes. | Unsupported Attribute lineage and metadata: not positioned as core on fullcontact.com for typical P&C paths, or unknown—verify. Market‑map placeholder only—treat support level as unverified until researched. | Unsupported Attribute lineage and metadata: not positioned as core on verisk.com for typical P&C paths, or unknown—verify. Curated seed aligned to vendor documentation; re‑validate before RFP reliance. |
Latency, freshness, and fallbacks SLAs, circuit breakers, and degradation modes when upstream latency spikes. | Unsupported Latency, freshness, and fallbacks: not positioned as core on fullcontact.com for typical P&C paths, or unknown—verify. Market‑map placeholder only—treat support level as unverified until researched. | Native Latency, freshness, and fallbacks: positioned as native or first‑class on verisk.com. Curated seed aligned to vendor documentation; re‑validate before RFP reliance. |
Score and model explainability Reason codes, adverse-action readiness, and challenger or champion controls for scoring. | Partial Score and model explainability: often partial, partner‑mediated, or LOB‑specific—confirm on fullcontact.com. Market‑map placeholder only—treat support level as unverified until researched. | Partial Score and model explainability: often partial, partner‑mediated, or LOB‑specific—confirm on verisk.com. Curated seed aligned to vendor documentation; re‑validate before RFP reliance. |
Geospatial and peril signals Footprints, hazard layers, geocode confidence, and uncertainty communication for underwriting and claims. | Native Geospatial and peril signals: positioned as native or first‑class on fullcontact.com. Market‑map placeholder only—treat support level as unverified until researched. | Partial Geospatial and peril signals: often partial, partner‑mediated, or LOB‑specific—confirm on verisk.com. Curated seed aligned to vendor documentation; re‑validate before RFP reliance. |
Contract testing and sandboxes Non-production sandboxes, fixture catalogs, and contract tests for integrators. | Unsupported Contract testing and sandboxes: not positioned as core on fullcontact.com for typical P&C paths, or unknown—verify. Market‑map placeholder only—treat support level as unverified until researched. | Partial Contract testing and sandboxes: often partial, partner‑mediated, or LOB‑specific—confirm on verisk.com. Curated seed aligned to vendor documentation; re‑validate before RFP reliance. |
Metering and cost transparency Clear metering for batch versus API, overage economics, and quota visibility for finance. | Partial Metering and cost transparency: often partial, partner‑mediated, or LOB‑specific—confirm on fullcontact.com. Market‑map placeholder only—treat support level as unverified until researched. | Partial Metering and cost transparency: often partial, partner‑mediated, or LOB‑specific—confirm on verisk.com. Curated seed aligned to vendor documentation; re‑validate before RFP reliance. |