What IBM’s IDTrust Listing Means for Enterprise AI-Agent Identity

The Hashgraph Group’s (THG) IDTrust now appears in the IBM Cloud Catalog as a third-party identity platform for AI agents, smart devices and people. Announced as part of a global partnership in September 2026, the listing gives IBM customers a way to discover the Hedera-based product. Its proposed enterprise use is more specific than identifying an agent: it is to help determine whether that agent is authorized to act. 151718

What the IBM partnership enables

IBM’s catalog identifies THG as IDTrust’s provider, while IBM’s partner directory lists SaaS and on-premises deployment options. That makes the product visible through IBM’s enterprise channels; it does not mean IBM built IDTrust or that every IBM customer uses it. 1519

THG says it qualified for IBM Silver Partner status and signed an Embedded Solution Agreement covering IBM cloud and AI technologies. The agreement allows THG to integrate IBM technology into its own products. These are partner and product-integration arrangements, distinct from the catalog listing that helps customers find IDTrust. 2

How IDTrust is intended to verify an AI agent

THG describes IDTrust as a platform for issuing, verifying and governing digital credentials for humans, machines and AI agents. Its product description says actors receive Hedera-based decentralized identifiers, while cryptographically verifiable credentials provide claims that another party can check. Hedera serves as the platform’s trust anchor. 18

For an enterprise, the Know Your Agent question is whether an agent presenting an identity also has valid authority for a particular action. A credential can supply evidence of identity or delegated permission, but an organization still has to decide whether that evidence satisfies its access rules. The partnership targets that authorization problem; a verifiable identity alone is not blanket permission to use every tool or system. 21118

THG also describes a proposed path for identity checks in agent workflows using Model Context Protocol (MCP) servers, including workflows involving IBM watsonx Orchestrate. The idea is to check credentials when an agent uses a connected tool and retain evidence that can be audited later. The cited material does not establish that every such integration is live or document its results in a customer environment. 810

What is deployed—and what remains to be shown

Reports say an unnamed European telecom provider uses IDTrust to verify caller identity. That is a use case for the identity platform, not independent evidence that the provider has deployed the AI-agent verification workflow described above; the available reports do not establish the deployment’s scale or outcomes. 1011

IBM is also listed as a member of Hedera’s governing council. The IDTrust arrangement moves beyond that network-level association to a commercial product offered through IBM’s catalog. Neither council membership nor a marketplace listing, however, guarantees IDTrust’s performance in a particular enterprise deployment. 1520