Construct the request body with the customer modules array listing the desired module keys such as the fraud and KYC module identifiers
Include the PII fields in the body: first name, last name, date of birth, address, SSN or last four digits, email, and phone as available
POST to the ID+ endpoint using your Socure SDK key in the Authorization header
Parse the top-level decision field for an overall accept, refer, or reject recommendation
Inspect the individual module-level scores and reason codes within the modules object of the response
Store the reference ID from the response for audit trail and potential manual review escalation
Known gotchas
Socure module keys are account-specific; using a module key not provisioned on your account returns an error rather than a default result
PII completeness significantly affects score confidence; missing fields such as SSN or date of birth will reduce match accuracy and may trigger automatic refer decisions
Socure's decision thresholds are configurable per environment; ensure your production configuration matches your risk policy before go-live
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