Obtain your API credentials (workflow token and secret) from the Alloy dashboard and base64-encode them for HTTP Basic auth.
Create an entity evaluation by POSTing to the evaluations endpoint with the person's PII (name, date of birth, SSN or last 4, address) inside a data object, along with the workflow_token to route the evaluation through the correct decisioning workflow.
Parse the synchronous response: the evaluation returns a summary outcome (Approved, Denied, Manual Review, or Pending) along with individual data source responses (credit bureau, document verification, etc.).
If outcome is Manual Review, implement a flow to collect additional identity documents from the user and submit them via the documents endpoint linked to the evaluation token.
Retrieve the final decision from the evaluation object once all steps complete; store the evaluation_token for future reference and for linking any ongoing monitoring.
Handle webhooks from Alloy for asynchronous updates if any data sources do not respond synchronously, updating your internal KYC status accordingly.
Known gotchas
Alloy workflows are highly configurable per customer — the exact data fields required, the data sources checked, and the scoring logic are all specific to your configured workflow; do not rely on generic documentation field lists without checking your own workflow configuration.
Sending PII fields that your workflow does not require is harmless, but omitting required fields causes a validation error rather than a soft decline; confirm required fields with your Alloy workflow settings.
Alloy evaluations generate a permanent audit record; never submit test PII with real SSNs or real personal data in sandbox — use the synthetic test identities Alloy provides for sandbox testing.
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