Execute a Verisk/ISO participation agreement to gain access to ClaimSearch; obtain your carrier's ClaimSearch participant ID and integration credentials from Verisk.
Choose your reporting method: manual entry via the ClaimSearch web portal for low-volume carriers, or automated system-to-system integration (API or ETL) for carriers needing real-time or batch reporting — Verisk provides integration specifications to participating carriers upon agreement.
Map your claim fields to ClaimSearch's required data elements: claim number, date of loss, coverage type, claimant name, SSN/EIN (where applicable and legally permitted), address, policy number, and paid/reserved amounts.
Submit claims at FNOL (initial record) and update the record at each significant claim event (reserve change, payment, closure) to keep the ClaimSearch record current; timely reporting is a contractual and, in some states, regulatory requirement.
Integrate ClaimSearch match alerts into your claims intake workflow: at FNOL, query ClaimSearch for the claimant's match record and surface any prior claims history or known-fraud flags to the adjuster.
Retain confirmation receipts for each submission for audit purposes; reconcile your submission log against ClaimSearch's acknowledgment reports to identify any failed submissions.
Known gotchas
ClaimSearch's API and data specifications are provided only to credentialed participants under a Verisk agreement; the technical integration guide is not publicly available — do not design integration schemas without the official Verisk specification.
Reporting personally identifiable information (SSN, date of birth) to ClaimSearch must comply with state privacy laws (e.g., CCPA, state insurance data security laws); implement data masking for query responses that exceed need-to-know scope.
Failure to update ClaimSearch records at closure or when a claim is found to be fraudulent undermines the database's value for all participants and may violate your participation agreement SLA.
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp