HOL Standards SDK

What does this agent do, and when should you use it?

HOL Standards SDK is a lightweight, HOL-maintained development kit containing reference implementations of Hashgraph Consensus Standards. It is distributed as the full `@hol-org/standards-sdk` package and the smaller `@hol-org/rb-client`, with an interactive CLI and runnable demonstrations. Its documented scope covers file storage, registries and indexing, recursive file loading, Smart Hashinals, agent communication, decentralized identity, auditable points, and transparency logs. Applications can use `RegistryBrokerClient` for agent search and chat, skill lifecycle queries, skill domain proofs, and UAID DNS TXT verification, while the HCS-10 demos exercise agent creation, registration, connection, and messaging. The SDK runs inside the adopter's JavaScript or TypeScript application; network transports, Hedera credentials, Registry Broker endpoints, and optional payment or ledger-authentication packages remain deployment responsibilities.

An application imports RegistryBrokerClient and connects to a Registry Broker using an API key or baseUrl. The client can call requestSkillVerification for a named skill version, obtain a DNS TXT challenge through createSkillDomainProofChallenge, and submit it through verifySkillDomainProof; getSkillStatus returns the trust tier, next steps, and any preview status URL. For HCS-14 UAID profiles, verifyUaidDnsTxt checks and can persist an _uaid.<nativeId> TXT proof, while getVerificationDnsStatus reads or refreshes its status. The HCS-10 demo creates and registers Alice and Bob, connects them, exchanges small messages, and handles larger messages using recursive storage; creation state can be written to .env for resumption after interruption. Separate inscription examples handle text, URLs, and file buffers and create Hashinal NFTs from URLs, buffers, or text. The pnpm run cli launcher exposes Registry Broker, OpenRouter, chat-history, ledger-authentication, and HCS-10 demonstrations.

1. Hedera developers implementing HCS-1, HCS-2, HCS-3, HCS-7, HCS-10, HCS-11, HCS-20, or HCS-27 in a TypeScript application.
2. Agent-platform teams that need Registry Broker discovery, chat, and lifecycle or trust-status checks for versioned skills.
3. Skill publishers requesting verification for a specific release and proving control of its domain through DNS TXT.
4. Decentralized-identity developers validating and persisting _uaid.<nativeId> DNS proofs for HCS-14 UAIDs.
5. Prototype teams demonstrating registration, connection, message exchange, and interrupted-creation recovery between two HCS-10 agents.
6. Applications that need only Registry Broker functionality and prefer a smaller client without bundled network transports.

How do you install or deploy this agent?

Install the full SDK under the current HOL scope:

npm install @hol-org/standards-sdk

The documented legacy scope remains available:

npm install @hashgraphonline/standards-sdk

For Registry Broker functionality alone, install the smaller client:

npm install @hol-org/rb-client

@hol-org/rb-client bundles no network transports. Core agent search and chat require a fetch implementation. X402 purchases and payments require axios, x402-axios, and x402; EVM ledger authentication requires viem; Hedera ledger authentication requires @hashgraph/sdk.

To run repository demos, clone the project and install its dependencies:

git clone https://github.com/hashgraph-online/standards-sdk.git
cd standards-sdk
npm install

Create the environment file:

cp .env.example .env

Populate the demonstrated settings:

HEDERA_ACCOUNT_ID=0.0.12345
HEDERA_PRIVATE_KEY=your_private_key_here
HEDERA_NETWORK=testnet
REGISTRY_URL=https://moonscape.tech

The supplied material does not specify a Node.js version.

How do you use this agent?

Start with the interactive launcher to inspect demos, required environment variables, and helper scripts:

pnpm run cli

Run the Registry Broker or HCS-10 demos directly:

npm run demo:registry-broker

npm run demo:hcs-10

A minimal skill-lifecycle lookup uses RegistryBrokerClient as follows:

import { RegistryBrokerClient } from '@hashgraphonline/standards-sdk';

const client = new RegistryBrokerClient({
  baseUrl: 'https://hol.org/registry/api/v1',
});

const status = await client.getSkillStatus({
  name: 'registry-broker',
  version: '1.0.0',
});

console.log(status.trustTier);
console.log(status.nextSteps);
console.log(status.preview?.statusUrl ?? null);

The corresponding runnable demo is:

pnpm -C standards-sdk run demo:registry-broker-skill-status -- --skill-name=<name> --skill-version=<version> --base-url=<broker-api-url>

For skill-domain verification, configure REGISTRY_BROKER_API_KEY, request a challenge, publish its TXT value, and submit the token:

import { RegistryBrokerClient } from '@hashgraphonline/standards-sdk';

const client = new RegistryBrokerClient({
  apiKey: process.env.REGISTRY_BROKER_API_KEY,
});

await client.requestSkillVerification({
  name: 'demo-skill',
  version: '1.0.0',
  tier: 'basic',
});

const challenge = await client.createSkillDomainProofChallenge({
  name: 'demo-skill',
  version: '1.0.0',
  domain: 'example.com',
});

const challengeToken = challenge.txtRecordValue.replace(/^hol-skill-verification=/, '');

await client.verifySkillDomainProof({
  name: 'demo-skill',
  version: '1.0.0',
  domain: 'example.com',
  challengeToken,
});

What are this agent's strengths and limitations?

How does this agent compare with similar options?

Key facts side by side with the most closely related agents.

How does FollowAgents rate this agent?

FAQ