Retrieve SentiLink synthetic identity risk scores for applicant screening
domain: docs.sentilink.com · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Authenticate API requests using HTTP Basic Auth with your SentiLink account ID and token (YOUR_ACCOUNT_ID:YOUR_TOKEN).
POST an application payload to the SentiLink scores endpoint containing the applicant's PII fields required for the product you have licensed (e.g., SSN, name, date of birth, address for the Synthetic Fraud Score).
Parse the synchronous response to extract the score value (typically 0–1000) and any reason codes provided; higher scores indicate higher synthetic identity risk.
Apply your institution's configured score thresholds to auto-approve low-risk applicants, auto-decline high-risk ones, and send mid-range applicants to manual review.
Log the SentiLink request ID from the response for dispute resolution and audit trail purposes.
Ensure your integration only submits data for permissible purposes under your contract and applicable law (FCRA permissible purpose if used as a consumer report).
Known gotchas
SentiLink offers multiple products (Synthetic Fraud Score, ID Theft Score, Demand Deposit Account Score); each has distinct input requirements and score scales—confirm which product you are licensed for.
SSN is required for the core synthetic fraud score; if the applicant does not have an SSN, you cannot obtain a meaningful score and must use an alternate signal.
Reason codes must be surfaced in adverse action notices if SentiLink is used as a consumer reporting agency; consult legal on FCRA compliance requirements.
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?