Standards Sdk is live · free · last verified 23 Oct 2026 · viability monitor
Standards Sdk
Open-source TypeScript SDK for building agent identity, registries and communication on the Hiero Consensus Specifications
The Standards SDK makes sense when a standards auditor will eventually ask which HCS revision you implemented and you want the answer from the organization that maintains the specs. It is a toolkit, not a product: budget engineering hours and pick it only when HOL alignment is already on your roadmap. For a working agent registry this week, start with the Registry Broker skills path rather than hand-coding HCS-10 and HCS-11.
Verdict generatedVerified 21d ago · liveness 65/100 · cite: rightaichoice.com/tools/standards-sdk
- TypeScript developers implementing HCS-11 identity profiles, HCS-10 communication or HCS-14 universal agent IDs
- Registry and discovery platform teams integrating HCS-2 registries and HCS-21 adapter registries
- Identity and attestation vendors with HOL conformance or certification obligations
- Agent-platform engineers wiring Discover, Delegate, Register and Interact into a product
- Non-developers who want a ready-to-use identity application rather than a library
- Teams that need a hosted identity console with an admin UI this quarter
- Projects with no plan to align to HOL-specific standards or conformance requirements
We scan live Reddit threads, YouTube comments, X posts, G2 reviews and other communities — and hand you an honest verdict in under a minute.
- Honest verdict, not marketing
- Real pros & cons from real users
- Attributed quotes with receipts
3 free scans · no card needed
Skip Standards SDK if you need a clickable identity console for stakeholders this quarter or your stack isn't TypeScript and you don't want to port a reference implementation.
Budget engineering hours before value: the package is free under MIT, but the identity, registry and trust modules are building blocks you assemble yourself.
At $0 under the MIT license, the Standards SDK costs nothing in licence fees and everything in engineering hours — compare it against paying for a managed identity or agent-registry service, not against another free SDK. Sized for teams with a live HOL roadmap; if you have no conformance obligation, a managed alternative is cheaper once you count the build.
In short
Standards Sdk — Open-source TypeScript SDK for building agent identity, registries and communication on the Hiero Consensus Specifications. Best for TypeScript developers implementing HCS-11 identity profiles, HCS-10 communication or HCS-14 universal agent IDs, Registry and discovery platform teams integrating HCS-2 registries and HCS-21 adapter registries, Identity and attestation vendors with HOL conformance or certification obligations. Free to use.
What is Standards Sdk?
Standards Sdk — Open-source TypeScript SDK for building agent identity, registries and communication on the Hiero Consensus Specifications. Best for TypeScript developers implementing HCS-11 identity profiles, HCS-10 communication or HCS-14 universal agent IDs, Registry and discovery platform teams integrating HCS-2 registries and HCS-21 adapter registries, Identity and attestation vendors with HOL conformance or certification obligations. Free to use.
The Standards SDK is the open-source JavaScript/TypeScript library HOL maintains so developers can implement the Hiero Consensus Specifications without hand-rolling protocol logic. Install @hashgraphonline/standards-sdk from npm and you get reference implementations for the agent-infrastructure standards HOL publishes as part of the Hiero Project under Linux Foundation Decentralized Trust: HCS-11 identity profiles with a registration workflow that returns a UAID, HCS-10 agent communication with session handshakes and task exchange, HCS-2 discovery registries, HCS-14 universal agent IDs, HCS-21 adapter registries, HCS-13 schema validation, HCS-20 auditable points, HCS-25 AI trust score methodology and HCS-28 agent transparency. It is modular by design. Pull the HCS modules your stack needs and leave the rest, then exercise an implementation with the bundled CLI before it ships into a product. Processing runs client-side, so the library does not tie you to a hosted service. Around the SDK, HOL ships three surfaces for its Registry Broker, a live universal index that routes across seven protocols: @hol-org/registry Registry Skills that teach Claude, Codex, Cursor and OpenClaw to search, register and chat through the broker API; the typed @hol-org/rb-client REST client covering discovery, registration, chat, delegation and analytics; and the @hashgraphonline/registry-broker-codex-plugin, which adds delegate, findAgents, summonAgent and sessionHistory over MCP stdio. HOL documents Discover, Delegate, Register and Interact as the four builder steps. Who it's for: wallet teams, registry and discovery builders, identity and attestation vendors, and agent-platform engineers who carry HOL conformance obligations. HOL's open-source dashboard reports 2.9M npm plus PyPI downloads across 13 npm and 4 PyPI packages and 6.1K GitHub stars. This is a developer library, not an identity console — teams wanting a hosted admin UI should look at managed registry products instead.
Key features
- @hashgraphonline/standards-sdk reference implementations from npm
- HCS-11 identity profile registration returning a UAID
- HCS-10 agent communication with session handshakes and task exchange
- HCS-2 discovery registries for agent listings and metadata
- HCS-14 universal agent ID and HCS-21 adapter registry modules
- HCS-25 AI trust score methodology and HCS-28 transparency registry
- HCS-13 schema validation and HCS-20 auditable points
- HCS-19 AI agent privacy compliance module
- HCS-3 resource linking and HCS-18 flora discovery protocol
- Modular package so you adopt only the components you need
- TypeScript/JavaScript library with all processing client-side
- Command-line interface for testing and debugging implementations
- @hol-org/rb-client typed REST client for discovery, registration, chat, delegation and analytics
- @hol-org/registry Registry Skills consumable as MCP context or native skill format
- @hashgraphonline/registry-broker-codex-plugin over MCP stdio
Behind the verdict
Reach for the Standards SDK when you are building the registry, identity or communication layer itself and the spec is the contract. That covers wallet teams adding HCS-11 profiles, registry builders wiring HCS-2 discovery plus HCS-21 adapters, and attestation vendors who need HCS-25 trust scores or HCS-28 transparency in their product rather than bolted on later. The strongest argument for it is provenance. HOL co-authors the Hiero Consensus Specifications and maintains the implementation, so a conformance question lands with the same organization that wrote the revision. In practice that saves the archaeology of diffing your code against a moving spec document. Modularity is the second draw. You adopt HCS-13 validation and HCS-14 IDs without dragging in payments or trust modules. The CLI earns its keep during debugging, when you want to inspect a registration or handshake before it reaches anything user-facing. Where it bites: this is a library that expects a TypeScript engineer with time to read standards. If you cannot justify that headcount this quarter, it is the wrong tool. We'd also skip it for projects with no intention of aligning to HOL-specific standards — you are paying a learning tax for interoperability you will not use. If you need something working now, the closest alternative is HOL's own Registry Broker skills path. @hol-org/registry across Claude, Codex, Cursor and OpenClaw plus the typed rb-client gets a search-register-chat loop running faster than hand-coding the HCS modules. Treat the SDK as the deeper layer you graduate into. One caveat on scope: the value depends on the seven-protocol index actually being live. Two recent news items point the same way — OpenAI and four rivals agreeing on a shared agent standard, and open-source projects
Limitations
- The SDK is documented for TypeScript/JavaScript; other languages require wrapping or porting.
- It is a reference implementation rather than a production-optimised library, so high-throughput scenarios may need performance tuning.
- All processing is client-side with no cloud service included, so there is no hosted runtime to fall back on.
- Because the value is alignment with HOL standards, teams not committed to HOL get little from it.
- HOL presents the standards program as partner-driven and invite-only, with 30+ founding partners, four standing subcommittees and 12+ working groups formed — the specifications and reference implementations come out of working groups rather than a fixed release cycle, so what exists at any moment depends on working-group output.
as of 2026-10-19
Researching Standards Sdk? Get your full AI stack in 60 seconds.
Free, no signup — tell us your goal and get tools matched to your budget & existing stack.
Is Standards Sdk still active?
Standards Sdk is live · free · last verified 23 Oct 2026 · viability monitor.
Viability score
How well maintained and how widely used is Standards Sdk? Built from what the vendor actually publishes (docs, changelog, tutorials, integrations, pricing), whether the site is live, and how much real users discuss it. How we calculate this
Last calculated: November 2026
How we score →What do users say about Standards Sdk?
What people actually say about Standards Sdk — is it worth it?
Our community sentiment research written Jul 30, 2026 is more than 90 days old, so it is being re-reviewed against current data and is not shown.
How we verified this
Every listed fact about Standards Sdk — pricing, features, links, status — is re-read from the vendor's own pages by our verification pipeline and each change is logged with a date; the last pass ran on 23 Oct 2026. Analysis is drafted with AI models and checked against our editorial standards before publishing; see how we verify.
Verification history
We have re-verified Standards Sdk 15 times since . Each pass re-reads the vendor's own pages and re-checks every listed field against that evidence; passes where nothing had changed are marked as such.
- — changed SSL certificate
- — changed features, who it suits, our verdict, description, who should skip it, summary, pricing tiers
- — changed hidden costs, use cases, who should skip it, setup time, our verdict, switching in, limitations, pricing fit, features, summary, switching out, description, who it suits
- — changed who should skip it, summary, description, who it suits, our verdict, features, pricing tiers
- — changed features, who it suits, integrations, our verdict, who should skip it, description, pricing tiers, summary
- — changed pricing fit, who it suits, description, our verdict, features, hidden costs, integrations, limitations, switching in, switching out, who should skip it, pricing tiers, setup time, summary, use cases
Showing the 6 most recent of 15 verification passes.
Free to cite with attribution — this page re-verifies continuously.
How much does Standards Sdk cost in 2026?
Standards Sdk: Free to use. Pricing last verified 23 Oct 2026.
Plans compared
Every published Standards Sdk tier, its price as the vendor publishes it, who it fits, and what it adds over the tier below. The 12-month cost projection follows.
| Plan | Price | Billing | Who it's for |
|---|---|---|---|
| Open Source (MIT) | Free | — | Development teams with a live HOL conformance roadmap who can absorb build time — wallet teams, registry builders and attestation vendors.Adds: Starting tier and the only published tier: MIT-licensed access to the HCS reference implementations, the CLI, the typed RB client and the Registry Broker skills and Codex plugin. |
12-month cost
Project the real annual outlay, including the implied monthly cost when only an annual tier is published.
Vendor list price only. Add-on usage, seat overages, and contract minimums are surfaced under Hidden costs & gotchas.
Where the pricing makes sense
The company stage and team size where Standards Sdk's pricing actually pencils out — and where peers do it cheaper.
At $0 under the MIT license, the Standards SDK costs nothing in licence fees and everything in engineering hours — compare it against paying for a managed identity or agent-registry service, not against another free SDK. Sized for teams with a live HOL roadmap; if you have no conformance obligation, a managed alternative is cheaper once you count the build.
Has Standards Sdk's pricing changed?
No plan price for Standards Sdk has moved since we began logging in Aug 2026; the pricing page is re-read on every verification pass.
Who should pick Standards Sdk?
Pick Standards Sdk if you are TypeScript developers implementing HCS-11 identity profiles, HCS-10 communication or HCS-14 universal agent IDs, Registry and discovery platform teams integrating HCS-2 registries and HCS-21 adapter registries, Identity and attestation vendors with HOL conformance or certification obligations, Agent-platform engineers wiring Discover, Delegate, Register and Interact into a product.
Look elsewhere if you are Non-developers who want a ready-to-use identity application rather than a library, Teams that need a hosted identity console with an admin UI this quarter, Projects with no plan to align to HOL-specific standards or conformance requirements, Solo builders without TypeScript capacity to read and apply spec-driven modules.
Skip it if Skip Standards SDK if you need a clickable identity console for stakeholders this quarter or your stack isn't TypeScript and you don't want to port a reference implementation.
GeneratedReal-world workflow fit
Concrete scenarios for the personas Standards Sdk actually fits — and what changes day-one when you adopt it.
You install @hashgraphonline/standards-sdk, run the HCS-11 registration workflow to get a UAID, and use the CLI to debug the profile before wiring it into your verifier.
Outcome: A conformant identity profile you can point at the published HCS-11 spec and a working UAID, without writing the registration flow from scratch.
You pull HCS-2 and HCS-14 modules into your listing service and use @hol-org/rb-client to query the Registry Broker by protocol and capability.
Outcome: Your platform returns ranked agent candidates for a task and can open a chat session across protocol boundaries through one typed client.
You add @hol-org/registry Registry Skills to Cursor or Claude, or install the Codex plugin for delegate, findAgents, summonAgent and sessionHistory over MCP stdio.
Outcome: Your assistant can search, register and chat through the broker API without you hand-writing each call.
Use cases
- Integrate HOL credential issuance into an identity system you already operate.
- Verify HOL presentations from holders inside a verifier application.
- Build a trust registry client on the standards-conformant implementation.
- Audit your own HOL implementation against the reference SDK.
- Prototype an HOL-compatible wallet using the CLI testing tools.
- Teach an AI coding assistant to search, register and chat through the Registry Broker API.
- Register an agent and obtain a UAID through the HCS-11 workflow.
- Route a task to the most capable available agent using the broker's ranked candidates.
Setup time & first value
How long it actually takes to get something useful out of Standards Sdk — broken out by persona, not the marketing-page minute.
Roughly 15-30 minutes for a developer to npm install @hashgraphonline/standards-sdk and complete an HCS-11 registration that returns a UAID using the CLI. Getting an agent routed through the Registry Broker with @hol-org/rb-client is an afternoon. Wiring a production verifier or registry with the trust and transparency modules (HCS-25, HCS-28) is a multi-week engineering project, not a same-day
Switching to or from Standards Sdk
How to bring data in from common predecessors and how to get it back out — written for the switcher, not the buyer.
- →From hand-rolled HCS code: swap your in-house registration and handshake logic for the HCS-11 and HCS-10 reference modules.
- →From a generic agent framework: add @hol-org/rb-client alongside your existing agent loop and route discovery through the Registry Broker.
- →From a bespoke MCP tool server: replace individual tool definitions with the @hashgraphonline/registry-broker-codex-plugin's delegate, findAgents, summonAgent and sessionHistory tools.
- ↗To a managed identity service: keep your HCS-11 profile schema as the data contract and replace the SDK registration call with the vendor's API.
- ↗To a generic agent registry: export your HCS-2 listings and remap fields to the alternative registry's listing schema.
Resources & guides
Tutorials & Learning
YouTube returned 6 videos for “Standards Sdk”, and we withheld 6: 6 did not mention Standards Sdk. We are showing none, because we could not prove any of them are about Standards Sdk.
Official links
What are the best Standards Sdk alternatives?
The closest alternatives to Standards Sdk we list are Taste Skill, OpenSpec and Tabby. Ranked by direct product-type match, not category overlap.
| Alternative | Pricing | Starts at | Last verified |
|---|---|---|---|
| Taste Skill | Free | Free | — |
| OpenSpec | Free | Free | — |
| Tabby | Freemium | Pricing not published | — |
Alternatives to Standards Sdk
View all
Taste Skill
Open-source SKILL.md rules that stop AI coding agents shipping generic frontend UI
Tools that pair well with Standards Sdk
Common stack mates teams adopt alongside Standards Sdk, with the specific reason each pairing earns its keep.
Taste Skill
Open-source SKILL.md rules that stop AI coding agents shipping generic frontend UI
OpenSpec
OpenSpec is a spec-driven development framework that keeps AI coding agents building the right thing — and proves it.
Tabby
Open-source, self-hosted AI code completion with an in-IDE answer engine, inline chat, and the Pochi agent
Standards Sdk vs its closest rival
Standards Sdk's closest head-to-head is with Spider Cloud — These tools serve completely different purposes. Choose Standards SDK if you are building HOL‑compliant decentralized identity systems and need verified reference code. Choose Spider Cloud if you need a cost‑effective, high‑performance web scraping API for AI agents or RAG pipelines, especially with its recent additions like Silk AI extraction and flat‑rate Unlimited plans. Verdict generated
Head-to-head comparisons
Standards Sdk vs Spider Cloud
These tools serve completely different purposes. Choose Standards SDK if you are building HOL‑compliant decentralized identity systems and need verified reference code. Choose Spider Cloud if you need a cost‑effective, high‑performance web scraping API for AI agents or RAG pipelines, especially with its recent additions like Silk AI extraction and flat‑rate Unlimited plans.
GeneratedStandards Sdk vs Voyage Ai
Voyage AI and Standards SDK serve completely different needs. Choose Voyage AI if you're building an enterprise RAG pipeline that demands high-accuracy retrieval on specialized domains like finance or legal, and you can invest in custom pricing. Choose Standards SDK if you're a developer implementing HOL decentralized identity standards and need a free, open-source reference implementation.
GeneratedStandards Sdk vs Temporal Ai
Choose Temporal AI if you need bulletproof reliability for long-running workflows and AI agents; choose Standards SDK if you are implementing HOL decentralized identity standards. They solve entirely different problems and are not direct competitors.
GeneratedFrequently asked questions
Best-of guides
For makers of Standards Sdk
- Get a Verified Listing for Standards Sdk ($39): a written decision within 1 working day.
- Free listing for another tool: Free reviews are decided in order, within 3 weeks of the review starting.
Used Standards Sdk? Help shape our editorial sentiment research.