HOL Standards SDK

Implement HCS standards, agent discovery, and trustless communication in your applications.

Stars
★ 1.3k
Last updated
1mo ago
License
Apache-2.0
Primary language
TypeScript

At a glance

How it runs
Library / SDKCLIFramework
Works with
Platform-specific
Setup effort
Medium · a few setup steps
You'll need
npm or pnpmHedera credentials for Hedera demosA fetch implementation for core agent search and chat flowsShell / CLINetwork accessLocal filesystem
Typical use
Hedera developers implementing HCS-1, HCS-2, HCS-3, HCS-7, HCS-10, HCS-11, HCS-20, or HCS-27 in a TypeScript application.
Not a fit if
  • Teams seeking a general protocol stack outside the Hedera/HCS ecosystem
  • Users looking for a ready-made chatbot
  • Teams requiring documented compatibility with a specific model platform
Website
hol.org ↗ set on GitHub
Maintenance
Commits in the last 6 monthslast commit 2026-10-19latest release v0.1.192 (2026-10-19)+0.6 ★/day over 7 days

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.

Key setup facts

Pulled from the install and usage notes below. The project README has the current values.

Install / run
  • npm install @hol-org/standards-sdk
  • npm install @hashgraphonline/standards-sdk
  • npm install @hol-org/rb-client
Environment variables
HEDERA_ACCOUNT_ID HEDERA_PRIVATE_KEY REGISTRY_URL REGISTRY_BROKER_API_KEY
Config files
.env.example .env

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?

Pros
  • One SDK covers eight explicitly listed HCS standards and supplies concrete HCS-10 communication and Registry Broker reference flows.
  • Teams can choose the full SDK or the smaller, transport-free @hol-org/rb-client to control integration scope and dependencies.
  • Skill verification combines name-and-version lifecycle status with DNS TXT domain proof, while UAIDs have a separate HCS-14 DNS verification API.
  • The HCS-10 demo records agent-creation progress in real time and can resume after an interruption.
  • The interactive CLI consolidates demonstrations, environment requirements, documentation links, and directly runnable scripts.
Limitations
  • The standards and advanced workflows center on the Hedera/HCS ecosystem, so projects using other ledgers or protocols need adaptation.
  • Full demos require a Hedera account, private key, network, and Registry URL rather than only a package-install command.
  • @hol-org/rb-client includes no network transport, and payment or ledger authentication introduces several optional dependency sets.
  • The source does not state a supported Node.js version or document native ChatGPT, Codex, Claude, or model-API compatibility.
  • Costs for Registry Broker access, Hedera transactions, agent funding, and X402 payments are not documented.

How does this agent compare with similar options?

Compared with the complete @hol-org/standards-sdk, @hol-org/rb-client contains only the Registry Broker client, has a smaller footprint, and bundles no network transports. Choose the full package for HCS implementations, HCS-10 flows, and the broader demos; choose the client when an application only needs discovery, chat, or Registry Broker integration and can add fetch, X402, EVM, or Hedera authentication dependencies as required.

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

Agent Source review Form / cost Stars Updated Language Full support on
HOL Standards SDK This agent 44 · Major gaps Library / SDK ★ 1.3k 1mo ago TypeScript —
Hindsight 68 · Some gaps Self-hosted serviceFreemium ★ 62k today Python OpenAI API · Claude API
Omnara Managed Agent Platform 68 · Some gaps Hosted serviceFreemium ★ 3.4k 1d ago Go Codex · Claude Code · Claude.ai · OpenAI API · Claude API
PenguinHarness 67 · Some gaps Desktop appFree + model costs ★ 3.3k today TypeScript OpenAI API · Claude API

How does FollowAgents rate this agent?

FollowAgents source review · FARS-2.1
Major gaps
44/ 100 5-point scale 2.2 / 5
Trust 11/29
Reliability 3/14
Adaptability 9/18
Convention 10/18
Effectiveness 7/13
Verifiability 4/8
Why each dimension lost points
Trust11 / 29 · 1.9/5

The README demonstrates environment variables for credentials and advises protecting private keys. Its examples also register skills, verify domain proofs, and persist DNS state; the HCS-10 demo automatically funds agents, creates topics, and registers them. The packet does not clearly document per-action confirmation or recovery controls. Data flows and external effects are described only in part, and dependency security is supported by a general audit claim. These areas receive partial credit. Package metadata, the maintainers pointer, security policy, and vulnerability contact support source attribution at 2; publisher identity remains unknown under the prompt.

Reliability3 / 14 · 1.1/5

The README, package.json, and export entry point consistently show an SDK spanning multiple HCS standards, with build, type-check, and demo commands. However, the README presents a HOL SDK while package metadata retains the older @hashgraphonline scope and also describes @hol-org distributions. Dependencies are declared, but the packet provides no reproducible lock evidence, availability guarantees, or failure-mode guidance. Self-consistency and dependency availability therefore receive partial scores; the sample provides no evidence about failure messages.

Adaptability9 / 18 · 2.5/5

The README targets developers building Hedera applications and lists supported standards, CLI use, demo paths, optional client dependencies, and Node/browser package outputs. This supports several ordinary scenarios and environments, but does not clearly define unsupported use cases or capability boundaries. The sampled SKILL.md is only a pricing-metadata demo fixture and provides no assessable trigger conditions or audience guidance, so trigger precision receives 1.

Convention10 / 18 · 2.8/5

The README is organized around quick start, documentation, standards, demos, security, and contribution guidance, and includes installation commands, code examples, and demo entry points. The license file and package metadata both identify Apache-2.0, earning full credit. The old and new package scopes coexist, and the version is a canary; the sample includes no changelog or clear migration history. The security policy names a supported version and reporting channel, and the README points to maintainers, but update responsibility and support scope remain limited.

Effectiveness7 / 13 · 2.7/5

The SDK groups implementations for multiple standards and gives target developers copyable client examples, demos, and CLI guidance. The packet does not quantify benefits, resource use, or deployment and maintenance costs. Broad functionality and optional dependencies show intended utility but do not establish value relative to complexity, so cost-benefit receives 1.

Verifiability4 / 8 · 2.5/5

README install commands, examples, and demos point to concrete interfaces or script names, while package metadata and exports corroborate the SDK's scope. Core capability claims are still primarily self-described in the README, with no test results or independent corroboration in this sample. The documentation does not consistently distinguish implemented capabilities, demo behavior, and user-facing expectations, so cross-source corroboration and fact-versus-inference separation receive partial scores.

Risks and how to mitigate them
  • Before running demos, account for automatic agent funding, on-chain topic creation, registration, and persisted state; the sample does not explain confirmation and recovery controls for each side effect.
  • Credential examples involve Hedera private keys. Although environment variables are recommended, access to environment files and the runtime environment still needs to be controlled.
  • The packet shows both the legacy package scope and HOL-scoped distributions; check actual release information alongside the version listed in the security policy.
Evidence confidence: Low Reviewed Nov 08, 2026 Reviewed revision 04f97c87da60
See the full review method →
Maintain this project? Add the FARS badge to your README

The badge shows the current review score and verdict and links back to this page. It refreshes about once an hour after a re-review.

FARS

[![FARS review](https://followagents.com/badge/standards-sdk.svg)](https://followagents.com/en/agents/standards-sdk)
<a href="https://followagents.com/en/agents/standards-sdk"><img src="https://followagents.com/badge/standards-sdk.svg" alt="FARS review"></a>

Recent releases

Latest entries from the project's GitHub Releases. Notes are quoted from upstream as written, not rewritten or tested by FollowAgents.

  1. v0.1.192
    Release notes excerpt
    Documentation - Standards SDK docs: https://hol.org/docs/libraries/standards-sdk/ <!-- Release notes generated using configuration in .github/release.yml at v0.1.192 --> What's Changed Other Changes * fix(hcs-25): resolve ans trust discovery agents by uid by @chou-godaddy in https://github.com/hashgraph-online/standards-sdk/pull/185 Full Changelog: https://github.com/hashgraph-online/standards-sdk/compare/v0.1.191...v0.1.192
    View on GitHub ↗
  2. v0.1.191
    Release notes excerpt
    Documentation - Standards SDK docs: https://hol.org/docs/libraries/standards-sdk/ <!-- Release notes generated using configuration in .github/release.yml at v0.1.191 --> What's Changed Other Changes * feat(hcs-25): add ans-trust-discovery adapter and collector by @chou-godaddy in https://github.com/hashgraph-online/standards-sdk/pull/184 New Contributors * @chou-godaddy made their first contribution in https://github.com/hashgraph-online/standards-sdk/pull/184 Full Changelog: https://github.com/hashgraph-online/standards-sdk/compare/v0.1.190...v0.1.191
    View on GitHub ↗
  3. v0.1.190
    Release notes excerpt
    Documentation - Standards SDK docs: https://hol.org/docs/libraries/standards-sdk/ <!-- Release notes generated using configuration in .github/release.yml at v0.1.190 --> What's Changed Other Changes * feat(hcs-25): add signal collectors for end-to-end trust-score collection by @kantorcodes in https://github.com/hashgraph-online/standards-sdk/pull/181 Full Changelog: https://github.com/hashgraph-online/standards-sdk/compare/v0.1.189...v0.1.190
    View on GitHub ↗

FAQ

Does core search and chat require the Hedera SDK?
No. Core agent search and chat in @hol-org/rb-client require only a fetch implementation; @hashgraph/sdk is needed specifically for Hedera ledger authentication.
What access is needed for skill-domain verification?
The example uses REGISTRY_BROKER_API_KEY to request verification and requires publishing the challenge as a DNS TXT record, so both Broker credentials and DNS control are needed.
Must an interrupted HCS-10 agent creation start over?
The demo records creation progress in .env, and the documented flow resumes from the saved point after interruption.
Are payment and ledger transports included?
No. The smaller client bundles no network transports; X402, EVM, and Hedera authentication each require additional packages.
What does it cost to operate?
The code is Apache-2.0 licensed, but the source gives no pricing for Registry Broker access, Hedera transactions, agent funding, or X402 payments.
Is HOL Standards SDK open source?
Yes. The source code is on GitHub (hashgraph-online/standards-sdk) under the Apache-2.0 licence.
Is HOL Standards SDK safe to use?
FollowAgents' FARS review (Nov 08, 2026) scored HOL Standards SDK 11/29 on trust and safety. None of the eight safety controls the review checks for was missing outright.
Is HOL Standards SDK still maintained?
Development has slowed: the latest commit on GitHub is from 2026-10-19, within the last six months but not the last 30 days. The latest release is v0.1.192 (2026-10-19).
Who makes HOL Standards SDK?
HOL Standards SDK is published on GitHub by the account hashgraph-online. FollowAgents has not verified which person or company is behind that account.
What is HOL Standards SDK's official website?
The project's GitHub repository lists https://hol.org as its website. That link is set by the repository owner; the source code itself is on GitHub (hashgraph-online/standards-sdk).
Was this page helpful?
View on GitHub ↗ Install ↓

Compare agents like this one

The same FARS review applied across the shortlist this agent qualifies for.

Related concepts