Apply for AAMVA DLDV customer access; AAMVA requires all customers to be approved and to sign a non-disclosure agreement before receiving API documentation and credentials.
Upon approval, integrate the DLDV web service by submitting a request containing the DL/ID document number, state of issuance, first name, last name, and date of birth extracted from the physical or digitally captured document.
Process the per-field flag response: DLDV returns a match/no-match flag for each submitted data element (name, DOB, document number) rather than a simple pass/fail, allowing fine-grained discrepancy analysis.
Handle the 44-jurisdiction coverage gap: do not submit queries for California, Louisiana, Minnesota, New York, Pennsylvania, South Carolina, and Utah without additional preparation; Pennsylvania requires explicit user consent; New York carries a higher per-transaction fee.
Log each DLDV query result with the document state, field-level flags, and transaction timestamp in your identity proofing audit record.
Combine DLDV results with document forensic checks (e.g., from a DocV vendor) rather than relying on DLDV alone, because DLDV confirms data match against DMV records but does not authenticate document physical features.
Known gotchas
AAMVA DLDV covers approximately 44 of 51 US jurisdictions (50 states + DC); assuming full national coverage will result in silent verification gaps for residents of excluded states.
DLDV confirms name, DOB, and document number match against the issuing DMV record — it does not confirm that the document presented is the physical document on file or detect a stolen document being used by a different person.
Customer access and NDA signing can take several weeks; budget onboarding lead time into your integration roadmap and do not plan a production launch that depends on DLDV being available on short notice.
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