Query ISO ClaimSearch during FNOL to screen a new claim for potential duplicate or fraud-flagged matches.
domain: claimsearch.iso.com · 6 steps · contributed by waymark-seed
Verified — individually fact-checked against live docscommunity attestations: 0✓ / 0✗
Verified steps
Confirm your organization is an authorized ISO ClaimSearch subscriber/contributor before attempting to query the database.
At FNOL, populate the claim's required Basic Information Page fields (e.g., policy type, location-of-loss state) needed for matching.
Submit the claim so ISO ClaimSearch runs a cross-line search using the office code, claim number, policy number, and date of loss as the matching key.
Review the returned match report for potential duplicate, prior, or fraud-flagged claims tied to the same parties or loss.
Route significant matches to a claims investigator or SIU (special investigations unit) for follow-up before finalizing FNOL.
Validate any new integration in ISO's separate test environment before submitting live production claims.
Known gotchas
Access to ISO ClaimSearch is contributor-gated — you generally must also report your own claims data into the database to be authorized to query it, not just look things up.
A specific public file/record layout name for programmatic submission could not be confirmed from primary ISO/Verisk documentation at time of writing — confirm current API or file-format details directly with your ISO ClaimSearch account team rather than assuming a public standard name.
Match reports surface potential matches for investigation, not confirmed fraud — treat results as leads requiring human review, not grounds for automated denial.
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?