TrustiryDevelopers
Trustiry.comGet an API key
Agent safety

Evidence before an agent acts.

Insert a decision checkpoint immediately before a sensitive action. Trustiry returns a stop or allow result without hiding the evidence gaps behind a single score.

Get an API keyOpen API reference
Action policypayment
Do not proceedSuspected impersonation
Relationship
Suspected impersonation
Confidence
High
Alternative
Available
Action-aware checks

Use a stricter policy when the consequence is higher

The same destination can require different handling depending on what the agent is about to do.

01

Login

Confirm the destination before credentials leave the agent.

02

Payment

Stop checkout when a reviewed relationship is missing or risk is high.

03

Document upload

Keep identity files and business documents away from unverified destinations.

04

Form submission

Inspect the receiver before sending personal or operational data.

05

Account creation

Avoid establishing a durable account relationship with an impersonator.

Contract example

Send intent. Receive an auditable decision.

request.http
POST https://api.trustiry.com/v1/agent-safety
Authorization: Bearer <tr_live_your_key>
Content-Type: application/json

{
  "url": "https://amaz0n-secure-login.example/checkout",
  "intended_action": "payment"
}
response.json
{
  "decision_id": "9d6f…",
  "normalized_domain": "amaz0n-secure-login.example",
  "relationship_status": "suspected_impersonation",
  "risk_status": "high_risk_signal_observed",
  "action": "payment",
  "action_allowed": false,
  "reason_codes": ["brand_impersonation_signal"],
  "official_alternative": "https://www.amazon.com",
  "confidence_class": "high",
  "unknowns": [],
  "expires_at": "2026-07-19T15:00:00.000Z"
}
Integration rules

Keep the safety boundary intact

These rules prevent a useful signal from turning into a misleading permanent label.

  1. 01

    Stop on false

    Treat action_allowed: false as a hard stop for the requested action.

  2. 02

    Show the context

    Preserve reason_codes, unknowns, confidence_class, and the dispute path in user-visible decisions.

  3. 03

    Respect expiry

    Refresh after expires_at. Never store a time-bounded decision as a permanent verdict.

  4. 04

    Minimize URL exposure

    Use POST and avoid copying paths or query strings into logs, analytics, or support tools.