Skip to content
Metamynd
The Digital Identity & Trust Layer for Artificial Intelligence

Every AI needs an identity before it can be trusted

VeriFAI gives every agent a verifiable, self-certifying identity (did:hedera / did:key) bound to an owner — KYC/KYB-verified for mainnet, and disclosed (not required) while you evaluate on sandbox or testnet — the foundation every other Metamynd capability builds on.

The problem

AI is acting without identity

Organisations deploy agents that call tools, access data and transact — yet cannot prove who or what is acting, who owns it, or what it is authorised to do. Without identity, there is nothing to govern, audit or trust.

VeriFAI

Verifiable identity for every AI

VeriFAI issues each agent a cryptographic DID whose key is self-certifying, links it to a legal owner (KYC/KYB-verified for mainnet; on sandbox and testnet verification is disclosed rather than required), and issues W3C Verifiable Credentials — all anchored on Hedera. It is the identity substrate the mandate, policy and evidence layers stand on.

Key Capabilities

What VeriFAI does

Agent Identity (DID)

A verifiable did:hedera per agent, anchored on an HCS registry topic.

Bring-your-own-key

Register a caller-controlled did:key; control proven via verify-key — we never see the private key.

Verified Legal Owner

KYC/KYB verification (assurance-graded) mints a verified-legal-entity credential; a bounded free tier lets you evaluate first, and the registry always discloses which one backs an agent.

Verifiable Credentials

Issue, present and verify W3C VCs, with BBS selective disclosure.

Public DID Resolver

Resolve any DID to its document — the key is derived from the DID, no lookup.

Delegated Authority

Bind what an agent may do to the verified principal that authorised it.

HCS Trust Registry

Discover identities via an HCS-2 registry across organisations and borders.

Architecture

How it fits together

VeriFAI layers a self-certifying DID model over Hedera Consensus Service, exposed through identity, credential and public-resolver APIs.

01DID & key management (did:hedera / did:key)
02Credential issuance & verification (VCs, BBS)
03HCS registry & anchoring
04Public DID resolver & APIs
Use Cases

Where it applies

  • Issue verifiable identities to a fleet of enterprise agents
  • Let an agent bring its own key (did:key) — MetaMynd never holds it
  • Show whether an agent's owner is verified, and how it was verified
  • Resolve and verify an external agent before granting access
Integrations

Works with your stack

Hedera Consensus ServiceW3C DIDs & Verifiable CredentialsMCPA2AAgent frameworksREST APIs
Outcomes

What good looks like

100%

of agents identifiable

0

keys held over the wire (BYOK)

Self-certifying

cross-org identity

See VeriFAI in action

Book a demo, or open the live product in the app to see it establish trust across your AI systems.