OpenAgent · SDK Hub
Two public SDKs.
One identity stack.
The public facade ships in TypeScript and Rust today. OAS, AEGIS, Arsenal, L1feID, and OATS stay visible as the lower layers developers can reason about and extend.
Live preview
One identity, in the language of your stack.
Compare the Rust and TypeScript public facades. Both expose the same OpenAgent path: create an agent, verify callers, enforce scopes, and broker credentials.
did:oas:l1fe:agent
z6MkiTBz1ymue...3djdX3mDooWp
01 · Pick your language
Every SDK, version 0.1.0
Current public launch surface. Planned language bindings remain off the installer path until their packages and examples pass release verification.
02 · Feature parity
One standard, many languages
8 features across 2 public SDKs. 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
These are the only one-line installers advertised for the public OpenAgent SDK facade until the next release train passes.
cargo add openagent-sdk --git https://github.com/OpenAgentID/openagent-sdknpm install github:OpenAgentID/openagent-sdk04 · 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 for the Rust facade; MIT-licensed website and docs.
Repositories
Rolling public in phases
Zero outbound telemetry. The SDKs never phone home. OpenAgentID repositories are being moved under the OpenAgentID organization as release checks pass.
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
MIT licensed under L1fe Labs, Inc.
OpenAgentID repositories are being moved under the OpenAgentID organization as release checks pass. All OpenAgentID SDKs, documentation, and reference implementations are MIT licensed under L1fe Labs, Inc.
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
Start with the facade, then drop into the feature stack when you need OAS identity, AEGIS verification, Arsenal credentials, or OATS reputation in more detail.