HCS‑14: Universal Agent Identifier (UAID)

HCS‑14 gives agents a single, portable identifier that works across Web2 and Web3. The SDK is network‑agnostic by default, with optional Hedera integrations.

• AID target (uaid:aid:) – deterministic from canonical agent data
• DID target (uaid:did:) – wraps an existing W3C DID and adds routing

You do not need a Hedera account. UAID creation for Web2/EVM and wrapping existing DIDs are fully offline. Hedera is only needed if you choose to issue/resolve did:hedera.

Quickstart

Generate a UAID in three common situations.

TypeScript

import { HCS14Client } from '@hashgraphonline/standards-sdk';
const hcs14 = new HCS14Client();

// AID: no DID yet
const uaidAid = await hcs14.createUaid(
  { registry: 'acme', name: 'Support', version: '1.0.0', protocol: 'a2a', nativeId: 'acme.example', skills: [0,17] },
  { uid: 'support' },
);

Go

import (
	"context"
	"fmt"
	"github.com/hashgraph-online/standards-sdk-go/pkg/hcs14"
)

client := hcs14.NewClient(hcs14.ClientOptions{})

// Resolve an existing UAID
result, err := client.Resolve(context.Background(), "uaid:did:example:123")
if err != nil {
	panic(err)
}
fmt.Printf("Resolved: %v, Profile: %s\n", result.Metadata.Resolved, result.Metadata.Profile)

Python

client = Hcs14Client()

# Resolve an existing UAID
result = client.resolve("uaid:did:example:123")
fmt.printf("Resolved: %v, Profile: %s\n", result.Metadata.Resolved, result.Metadata.Profile)

Visual Overview

UAID generation