Six languages.
One identity stack.
TypeScript, Rust, Python, Go, Swift, and Kotlin — one facade. OAS, AEGIS, Arsenal, and OATS (audit/trust signals — not a paid universal score) stay visible as the lower layers developers can reason about and extend.
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.
1·Rust — Component crates are on crates.io (oas-sdk, openagent-aegis-sdk, arsenal-sdk, agent-capability-token, …). The unified openagent-sdk façade crate is not published yet — use git for the façade when needed.
2·Python — Published to PyPI as openagentid-sdk. The import name is openagent_sdk.
3·TypeScript — Published to npm under the @openagentid scope.
4·Go — The module path publishes when the repositories open. Until then, use sdks/go from an openagent-sdk checkout.
5·Swift — The manifest lives at sdks/swift. Add it as a local package from an openagent-sdk checkout until the standalone package publishes.
6·Kotlin — Not yet on Maven Central. The repository is private during consolidation.
One command
per language.
TypeScript installs from npm and Python from PyPI today, and the Rust library crates (oas-sdk, openagent-aegis-sdk, arsenal-sdk, agent-capability-token) are live on crates.io.
The unified SDKs for the other languages install from git — org access required while the repositories consolidate under the OpenAgentID organization — and their registry publication (the unified Rust crate to crates.io, Kotlin to Maven Central) lands as each language passes release verification.
$npm install @openagentid/sdkPublished to npm under the @openagentid scope.
package ↗One standard,
many languages.
10 features across 6public 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.
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.
| Commitment | Status | Detail |
|---|---|---|
| Telemetry | Today | None. Zero outbound telemetry. |
| License | Today | Apache-2.0 OR MIT. |
| Repositories | Today | Rolling public in phases |
| SOC 2 Type II | Roadmap | Planned · Q3 2026 |
| Signed artifacts | Roadmap | Planned in 0.2.0 |
| SBOM | Roadmap | Planned in 0.2.0 |
| Build provenance | Roadmap | SLSA Level 3 by 0.3.0 |
1·Zero outbound telemetry. The SDKs never phone home. Repositories are private while they are consolidated under the OpenAgentID organization, and open publicly as release checks pass.
2·Roadmap items are tracked in Linear and published as they ship. No promises until they are verifiable.
Dual-licensed
Apache-2.0 OR MIT.
Repositories are private while they are consolidated under the OpenAgentID organization, and open publicly as release checks pass. All OpenAgentID SDKs, documentation, and reference implementations are dual-licensed Apache-2.0 OR MIT under L1fe Labs, Inc.
Drop below
the facade.
The SDK is a facade over independent libraries. When you are building infrastructure rather than an app, reach for the layer directly.
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.
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 with the facade, then drop into the feature stack when you need OAS identity, AEGIS verification, Arsenal credentials, or OATS audit signals in more detail.