Apply for DLDV access through AAMVA (aamva.org); applicants must be a commercial or government entity with a legitimate permissible purpose, sign an NDA, and receive approval from AAMVA before receiving documentation.
After approval, integrate with the DLDV web service using the WSDL and schema documents provided by AAMVA; the service uses a SOAP/XML request containing the DL/ID number, issuing state, name, date of birth, and optionally address fields.
Submit the verification request; the service queries the issuing jurisdiction's DMV in real time and returns a flag for each submitted data element indicating Match, No Match, or Unable to Verify.
Use the response flags to validate identity documents during onboarding; a full match across name, DOB, and DL number provides strong document authenticity evidence.
Log verification results with timestamps for compliance audit trails; many regulated industries (financial services, gig economy) require retention of verification records.
Handle the approximately 56 jurisdictions currently participating; for non-participating states, fall back to manual document review or alternative verification methods.
Known gotchas
AAMVA's DLDV covers roughly 44 jurisdictions as of mid-2026, representing approximately 73% of the US population — your workflow must handle unsupported states gracefully.
Pennsylvania requires explicit written consent from the individual before their data can be queried; New York carries higher per-transaction fees. Build jurisdiction-specific handling into your integration.
DLDV returns a match/no-match flag only — it does not return DMV record data. If the document data does not match, you receive a no-match without additional detail about which field failed.
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