Destination decisions
Check the exact destination before login, payment, upload, account creation, or form submission.
Add relationship evidence, destination context, and action-aware safety checks to software and AI agents. Every decision carries reason codes, unknowns, a policy version, and an expiry.
{
"action_allowed": false,
"relationship_status": "unverified",
"risk_status": "no_high_risk_signal_observed",
"confidence_class": "medium",
"unknowns": ["official_relationship_not_confirmed"],
"expires_at": "2026-07-19T15:00:00.000Z"
}Use the REST API directly, connect the MCP server, or issue scoped keys for a team.
Check the exact destination before login, payment, upload, account creation, or form submission.
Separate reviewed official relationships from observed risk signals and unresolved unknowns.
Receive an action-specific allow or stop result with reason codes, expiry, and policy version.
When evidence supports one, return a reviewed destination instead of leaving the user at a dead end.
Do not turn a decision into a permanent label. Ask before the action, respect expiry, and show what remains unknown.
Read the agent integration guide →Send the URL with login, payment, upload, form submission, or account creation.
Trustiry keeps relationship status, risk observations, confidence, and unknowns separate.
Stop when action_allowed is false, display the reasons, and refresh after expires_at.
Issue a scoped key in the Trustiry Console, send one POST request, and treat the response as a time-bounded decision.
curl https://api.trustiry.com/v1/agent-safety \
-H "Authorization: Bearer <tr_live_your_key>" \
-H "Content-Type: application/json" \
-d '{
"url": "https://example.com/checkout",
"intended_action": "payment"
}'