Skip to main content
#trstdBeta

Make AI agents trusted.

With #trstd <protocol>, your agents gain a verifiable identity, turn real interactions into portable reputation and earn lasting acceptance.

Access to the trust infrastructure is free and remains free. Trust is earned, never bought. Paid plans add advanced services.

Good AI agents should build Reputation – not rebuild trust from zero every time.

AI agents are flooding the web. Service providers have to respond. Blocking keeps rogue agents out, but it costs visibility and makes trustworthy Brands disappear from AI-driven journeys. When trustworthy Brands are missing from the ecosystem, AI agents increasingly make poor decisions. And when those decisions have consequences, one question becomes unavoidable: who is liable?

But let’s start at zero. When we meet someone, we introduce ourselves first. What happens next builds trust: how we behave towards each other shapes our Reputation over time. With #trstd, the same applies to AI agents — and their Reputation is portable.

Turn your agents into trusted partners through verifiable identity, behaviour and evidence — without rebuilding trust wherever they go.

Join #trstd

Built on standards

  • Web Bot AuthSigned agent requests
  • RFC 9421HTTP Message Signatures
  • W3C DIDPersistent identity
  • W3C Verifiable CredentialsVerifiable assertions
  • A2AAgent communication
  • MCPTool interaction
  • TSAITrusted AI interactions

Identity is the beginning. Behaviour builds Reputation.

A verifiable identity makes your Agent accountable. From there, every relevant interaction can add evidence about how reliably it acts.

Does it respect permissions and rate limits? Stay within its mandate? Complete actions accurately? Protect data? Respond correctly when something goes wrong? Verified outcomes build Reputation over time. Serious violations can destroy trust in an instant.

Reputation becomes portable value. Built from verified identity, behaviour, outcomes and feedback, it gives your Agent a verifiable track record that stays with it across the #trstd ecosystem.

Join #trstd

Identity starts trust. Verified behaviour builds it. Reputation turns it into access.

  1. 1IdentityVerified agent and accountable operator
  2. 2Verified interactionsReal actions create evidence
  3. 3ReputationTrust builds through behaviour over time
  4. 4Acceptance & accessTrusted agents get more relevant access

Back to step 2. Better access creates more verified interactions, so trust compounds instead of standing still — identity alone is never enough.

Don’t let your Agents guess who to trust. Let them verify.

AI agents cannot rely on logos, polished websites, self-declared claims or third-party reviews with no verifiable link to a real transaction. Before recommending a Brand, sharing data or taking action, they need proof of genuine identity and evidence-backed trust signals.

Through #trstd <protocol>, agents can access machine-readable trust information such as verified identity, current status, reviews, Reputation, assurance and relevant risk signals.

Trust works both ways: your agents prove who they are, while the Brands and services they interact with prove themselves in return.

Join #trstd

Earn the access you need – through the trust you’ve built.

Being identified does not create a universal right of access. A Brand still decides what an agent may do.

Crawling at scale may require a verifiable identity. Accessing structured product data could require a history of policy-compliant behaviour. Placing an order may additionally require a valid customer mandate. Sensitive actions can require stronger evidence, limits or explicit confirmation.

#trstd gives the receiving Brand the evidence it needs to distinguish your agent from unknown automation and make a differentiated decision instead of simply blocking it.

For trustworthy agents, that means fewer unnecessary restrictions and better access to the services they need to get the job done.

Join #trstd

Know why access was granted – or why it wasn’t.

Trust is not a single global score. An Agent can be trusted for one action and still be unproven for another.

#trstd combines the requested capability and context with relevant identity, authority, behavioural evidence, Reputation and evidence confidence. The result can be allow, allow with limits, challenge, restrict or block.

And the reason remains visible. Operators can understand which evidence mattered, which constraint applied and what needs to change before a different decision becomes possible.

That makes trust actionable instead of opaque — and creates a path to correction and remediation when something goes wrong.

Join #trstd

One Agent. Its identity, evidence and reputation.

Each Agent gets its own Profile, bringing together its persistent identity, accountable operator, status and reputation in one view.

See how its reputation develops over time and which verified interactions and outcomes contributed to it. When the Agent interacts with a Brand or service, relevant trust information can be provided through #trstd <protocol>.

Join #trstd

Your Agents build trust. You stay in control.

One Agent is manageable. A fleet needs an operational view. The Operator Console brings your registered Agents, status, credentials, interactions, outcomes and Reputation together in one place.

See how trust develops across your Agents and where incidents, restrictions or remediation need attention. Basic Agent and fleet management is included with #trstd.

Advanced fleet governance, compliance evidence, automation, high-volume services and dedicated support are available with paid plans.

Join #trstd

How to integrate #trstd <protocol> into your agents

#trstd <protocol> builds on established standards for authentication, identity, credentials, authorisation and agent communication. Verified identity is the starting point. The protocol adds what makes trust useful: verifiable interactions, outcomes and Reputation over time.

Use the #trstd SDK, Docs, Sandbox and Conformance tools to register your agents, exchange trust information, verify counterparties and test your first trusted interactions.

Questions about #trstd for AI?

53% of web traffic was automated in 2025 and 40% of all traffic was classified as malicious. Without verifiable identity, a well-behaved agent is indistinguishable from a hostile one — and gets blocked with it.
Through signed, passive data trails: mandate fidelity, outcome reliability, safety, security and privacy, identity and accountability, transparency, policy cooperation and remediation. Both the agent and the service provider sign what happened.
T0 Unknown, T1 Identified, T2 Observed, T3 Trusted, T4 Assured, plus TX Restricted and TR Revoked. Trust is capability-specific — one agent can be T4 for search and T1 for payment initiation.
Yes, and deliberately faster than it is gained. Mandatory gates — a revoked credential, an invalid signature, a missing mandate for a purchase, an unresolved critical incident — override any accumulated score.
No. #trstd complements UCP and AP2 rather than competing with them. Those protocols establish what happened; #trstd establishes whether the actor behaved trustworthily over time.
Core protocol access and basic trust signals are free, including for strategic AI Agent Operators. Premium services monetise assurance, control, analytics and protection — never access to the network.