Authenticate using HTTP Basic Auth with your Alloy API key and secret (YOUR_API_KEY:YOUR_SECRET) encoded in Base64 as the Authorization header.
Create an evaluation by POST-ing to the evaluations endpoint under your workflow, passing the entity data object containing the user's PII fields (name, address, date of birth, SSN last four or full as required by your workflow).
Alloy synchronously returns an evaluation result with an outcome field indicating 'Approved', 'Denied', or 'Manual Review', along with a summary of which data sources returned matches or flags.
Inspect the reasons array in the response to understand which rules triggered the outcome and which third-party data sources were queried.
For 'Manual Review' outcomes, use the Alloy dashboard or webhook events to manage the manual review queue; listen for the evaluation.updated webhook event to receive the final disposition.
Store the evaluation token and outcome against your user record; use the evaluation token to retrieve full details or to create a follow-up evaluation if additional data becomes available.
Known gotchas
Alloy workflows are highly configurable; the fields required in the evaluation payload depend entirely on what data sources your specific workflow is configured to call.
Some outcomes are synchronous and others are asynchronous depending on the data sources in your workflow; do not assume all evaluations return a final outcome immediately.
PII fields sent to Alloy are governed by your data processing agreement; confirm which fields you are contractually permitted to transmit before going 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