Submit a Verisk A-PLUS Auto Report Claims request via the UnderWriting API for auto loss-history underwriting
domain: gateway.verisk.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Obtain a bearer token from the Verisk Security Token Service using your consumer_key/consumer_secret and the client_credentials grant.
POST the primary driver's name and current address to https://gateway.verisk.com/underwriting/aplusauto/claims/v4 to search up to five years of auto loss and coverage history.
Parse the returned claims for both claims filed by the applicant and claims filed by others about the insured or the vehicle(s) to be insured.
Check the returned flags/indicators (At-Fault, Salvage, Mexico theft, Hurricane Katrina, Notice of Recall, prior repair estimates) as part of your rating/eligibility logic.
Request request/response schema samples from PLUWClientServices@verisk.com before finalizing your integration.
Known gotchas
The report can include claims about the insured or vehicle filed by other parties, not just the applicant's own claims — your matching logic needs to handle mixed-subject records correctly.
A-PLUS Auto and A-PLUS Property use different required-field structures (Driver fields vs. Insured Person fields) despite similar endpoint patterns — don't reuse one product's request template for the other.
The same 60-minute token expiry and caching requirement applies as with other Verisk UnderWriting API products.
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?