API-first integration Provides documented APIs suitable for carrier or insurtech engineering teams. | Partial API-first integration: often partial, partner‑mediated, or LOB‑specific—confirm on carpe.io. Seeded comparison value; corroborate with docs or implementation references. | Unsupported API-first integration: not positioned as core on nearmap.com for typical P&C paths, or unknown—verify. Market‑map placeholder only—treat support level as unverified until researched. |
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. | Partial Consent and permissible purpose: often partial, partner‑mediated, or LOB‑specific—confirm on carpe.io. Seeded comparison value; corroborate with docs or implementation references. | Partial Consent and permissible purpose: often partial, partner‑mediated, or LOB‑specific—confirm on nearmap.com. Market‑map placeholder only—treat support level as unverified until researched. |
Attribute lineage and metadata Field-level lineage, vintage, refresh cadence, and schema drift handling for attributes. | Native Attribute lineage and metadata: positioned as native or first‑class on carpe.io. Seeded comparison value; corroborate with docs or implementation references. | Native Attribute lineage and metadata: positioned as native or first‑class on nearmap.com. Market‑map placeholder only—treat support level as unverified until researched. |
Latency, freshness, and fallbacks SLAs, circuit breakers, and degradation modes when upstream latency spikes. | Partial Latency, freshness, and fallbacks: often partial, partner‑mediated, or LOB‑specific—confirm on carpe.io. Seeded comparison value; corroborate with docs or implementation references. | Partial Latency, freshness, and fallbacks: often partial, partner‑mediated, or LOB‑specific—confirm on nearmap.com. Market‑map placeholder only—treat support level as unverified until researched. |
Score and model explainability Reason codes, adverse-action readiness, and challenger or champion controls for scoring. | Native Score and model explainability: positioned as native or first‑class on carpe.io. Seeded comparison value; corroborate with docs or implementation references. | Native Score and model explainability: positioned as native or first‑class on nearmap.com. Market‑map placeholder only—treat support level as unverified until researched. |
Geospatial and peril signals Footprints, hazard layers, geocode confidence, and uncertainty communication for underwriting and claims. | Partial Geospatial and peril signals: often partial, partner‑mediated, or LOB‑specific—confirm on carpe.io. Seeded comparison value; corroborate with docs or implementation references. | Partial Geospatial and peril signals: often partial, partner‑mediated, or LOB‑specific—confirm on nearmap.com. Market‑map placeholder only—treat support level as unverified until researched. |
Contract testing and sandboxes Non-production sandboxes, fixture catalogs, and contract tests for integrators. | Partial Contract testing and sandboxes: often partial, partner‑mediated, or LOB‑specific—confirm on carpe.io. Seeded comparison value; corroborate with docs or implementation references. | Native Contract testing and sandboxes: positioned as native or first‑class on nearmap.com. Market‑map placeholder only—treat support level as unverified until researched. |
Metering and cost transparency Clear metering for batch versus API, overage economics, and quota visibility for finance. | Unsupported Metering and cost transparency: not positioned as core on carpe.io for typical P&C paths, or unknown—verify. Seeded comparison value; corroborate with docs or implementation references. | Partial Metering and cost transparency: often partial, partner‑mediated, or LOB‑specific—confirm on nearmap.com. Market‑map placeholder only—treat support level as unverified until researched. |