Use the Alloy API to run a decisioning workflow that combines identity verification, watchlist screening, and fraud signals into a single onboarding decision
domain: docs.alloy.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
POST to /v1/evaluations with entity data (name, address, SSN last 4, DOB) and the workflow_token identifying your configured workflow
Inspect the summary.outcome field in the response for the top-level decision (approved, denied, manual_review)
Iterate over the sources array to see which data partners (e.g., Experian, LexisNexis, OFAC) contributed to the decision
For manual_review outcomes, retrieve the reasons array and map each reason code to a human-readable description for the review queue
Use the journey_application_token from the response to fetch entity details or trigger a step-up challenge (e.g., document upload) via the same evaluation entity
Known gotchas
Alloy workflows are version-controlled; deploying a new workflow version does not automatically migrate in-flight evaluations
SSN-based matching in the US requires explicit consent capture and appropriate state disclosures before the evaluation call
The reasons array codes are workflow-specific; maintain a mapping table per workflow version to avoid stale code-to-text translations after workflow edits
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