Obtain the required permissible purpose certification and complete the SSA's eCBSV enrollment process including signing the user consent agreement
Collect explicit written or electronic consent from the end user authorizing SSN verification against SSA records before any API call
Submit the user's SSN, name, and date of birth to the eCBSV API endpoint using your enrolled credentials
Parse the response for the verification result which returns a match indicator for each submitted field rather than raw SSA data
Log the verification result, consent record, timestamp, and purpose code for each eCBSV query as required by the SSA agreement
Handle a no-match result by routing the user to an alternative verification path rather than auto-rejecting, as data entry errors can cause false no-matches
Known gotchas
eCBSV access requires a signed agreement with the SSA and is not available to all organizations; procurement and legal review timelines can be months
The service returns a match or no-match indicator, not the actual SSA record data; you cannot retrieve or display SSA information to the user
Transaction volume limits apply; exceeding your contracted volume may result in API errors or suspension, so implement rate limiting and monitoring
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