Order a Motor Vehicle Report (MVR) through Verisk's UnderWriting API using the submit/retrieve order flow
domain: gateway.verisk.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Authenticate against the Security Token Service (POST /token with Basic auth of consumer_key:consumer_secret and grant_type=client_credentials) to obtain a bearer token.
POST the driver's given name, surname, date of birth, driver's license state, and (where required) license number to https://gateway.verisk.com/underwriting/motorvehicle/order/v4 to submit the request and receive an Order Number.
Check the state-specific MVR Guidelines document, since required search fields vary by state — some states allow a name+DOB search while others mandate a license number.
Submit a second call to the MVR Retrieve Report endpoint with the Order Number to pull the Motor Vehicle Report or Index of Activity result.
Handle a 200 response with an empty body as a 'no record found' result rather than an error.
Known gotchas
MVR ordering is a two-call async pattern (submit for an Order Number, then retrieve) — a single POST does not return the report directly.
As of V4, license number is optional in several states (CA, FL, IN, ME, MI, MN, MO, NE, NH, NY, OH, OK, VA, WI, WY) but required in others, returning HTTP 400 if omitted where mandatory.
V4 also introduced HTTP 588 for response-schema validation errors — treat it distinctly from a standard 4xx/5xx in your error handling.
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?