The canonical DID Document profiles that define decentralized identifiers across the VeriTrust ecosystem. Each schema specifies the structure a verifier resolves and validates when establishing the identity of an agent owner, an agent, or a trust anchor.
VeriTrust identities are JSON-LD DID Documents conforming to the W3C DID Core data model. The three reference schemas below describe each role in the chain — the organization that owns an agent, the agent itself, and the trust anchor that underwrites the ecosystem. Every schema is versioned and resolvable, so any verifier can fetch the exact profile and validate a document against it.
The DID Document for an organization that owns and operates agents. The canonical DID is self-controlled did:web, with JOSE JWK verification methods and optional service endpoints.
The DID Document for an individual agent. The canonical DID is did:key, controlled by did:web:neksus.ai, with JWK verification methods and optional service fragments.
The DID Document for the VeriTrust trust anchor itself. The canonical DID is did:web:veritrust.vc, and the profile requires a signing key plus the core services that underpin resolution and accreditation.
The DID Resolver dereferences a VeriTrust DID to its DID Document and checks it against the matching schema, returning the verification methods and services declared for that identity.
When an agent presents its identity, VeriAgent validates the document structure against the Agent schema and confirms the controller chain back to a recognized Agent Owner and Trust Anchor.
Identities that conform to these profiles can be listed in the VeriTrust Registry, where accreditation status and trust relationships are published for third parties to consult.