OpenAgent · SDK Hub
Seven languages. One identity standard.
Every SDK is a thin client over OpenAgent's DID-native protocols. Same contracts, same crypto, same wire format -- in the language your team already ships.
did:oas:l1fe:agent
z6MkiTBz1ymue...3djdX3mDooWp
01 · Pick your language
Every SDK, version 0.1.0
Released together on 2026-04-12. Honest stability labels: beta ships with the reference contracts wired, alpha still has rough edges, planned is a spec waiting for implementation.
02 · Feature parity
One standard, many languages
26 features across 7 languages. This is what's shipping today. Green dots are wired and under test; amber has known gaps; dim dots are roadmap; dashes mean the feature does not apply to that runtime. Hover any row to read its contract.
03 · Install
One command per language
No config, no post-install scripts, no peer-dep gymnastics. If an install command fails on a supported platform, we treat it as a P1 bug.
cargo add openagent-sdknpm install @openagent/sdkpip install openagent-sdkgo get github.com/openagentid/openagent-go.package(url: "https://github.com/openagentid/openagent-swift", from: "0.1.0")implementation("id.openagent:openagent-sdk:0.1.0")npm install @openagent/vanilla04 · Compliance & security
Honest about what ships today
We do not claim certifications we have not earned. Here is what we commit to today and what we are working toward. SOC 2, signed artifacts, SBOM, and build provenance all land before we cut the GA tag.
Today
Telemetry
None. Zero outbound telemetry.
License
Apache-2.0 OR MIT
Repositories
Rolling public in phases
Zero outbound telemetry. The SDKs never phone home. Repositories are rolling open-source in phases through 2026.
On the roadmap
SOC 2 Type II
Planned · Q3 2026
Signed artifacts
Planned in 0.2.0
SBOM
Planned in 0.2.0
Build provenance
SLSA Level 3 by 0.3.0
Roadmap items are tracked in Linear and published as they ship. No promises until they are verifiable.
05 · Open source
Apache-2.0 or MIT. Your choice.
Repositories are rolling open-source in phases through 2026. All SDKs are dual-licensed under Apache-2.0 and MIT so you can pick whichever your organization prefers.
06 · Support
File an issue. Get an answer.
Three tiers, all staffed by the engineers writing the code. Enterprise tiers come with written SLAs -- the community channels run on best-effort.
GitHub Issues
Report bugs, request features, and ask questions. Issues across the SDKs are triaged by the OpenAgent team.
Discussions
Community Q&A, design conversations, and weekly-office-hours summaries.
Enterprise support
Guaranteed response times, private incident channels, and architecture review. SLA-backed tiers available.
Open-source channels are staffed best-effort during UTC business hours. SLAs, private incident bridges, and dedicated engineers are only available under an enterprise agreement. No SLA is implied for community channels.
Start building
Pick your language
Each page includes a quickstart, authentication, pagination, retry, webhooks, testing, and the full error catalog.