AI agent identity and decentralized trust
Decentralized Identity and DIDs
Portable identity, independent verification.
Standards-based identifiers and verifiable identity documents that bridge organizational ecosystems.
In practice
What this service does.
Give digital identities the ability to travel beyond a single provider. Connect verifiable identifiers and public keys through decentralized identity standards while keeping privacy and practical operations at the centre.
Best for
Digital credentials, identity ecosystems, cross-platform applications
Integration detail — endpoints, token shapes, SDKs and the standards each flow follows — lives in the developer portal.
Capabilities
- DID creation and resolution adapters
- DID document lifecycle and verification methods
- Key binding and controller verification
- Decentralized credential status integration
- Interoperability across selected DID methods
- Trust registry and resolver infrastructure
Capabilities describe what the service is built to do. Which of them a given tenant uses — and in which environments — is part of the configuration you choose.
Same family
More in AI agent identity and decentralized trust.
Verifiable identity for autonomous software, and identity that travels between organizations.
AI Agent Identity
Every autonomous agent needs a verifiable identity.
Agent identifiers, public keys, operating organization relationships and credential lifecycles.
Service detailsAgent Trust and Interoperability
Make independently operated agents recognizable.
Portable agent identity and verifiable claims across vendors and agent networks.
Service detailsVerifiable Identity Anchoring
Independent evidence for important identity records.
Cryptographic commitments to selected signed identity events, anchored to public ledgers.
Service detailsIdentity Event Ledger and Evidence
A reliable record of the identity lifecycle.
Tamper-evident identity event history for investigation, audit and trust verification.
Service detailsPut Decentralized Identity and DIDs to work.
Start with a development tenant and one application, or talk through the architecture first — tenancy, credential lifecycle and which parts stay in your own stack.
Packages and metered usage are set out on the pricing page; the figures themselves are agreed with our team against the services you need.