SDKs and package versions
Choose a published package and its matching runtime, exports and integration contract.
The current onboarding path uses TypeScript/JavaScript and the working starter:
| Public package | Version | Runtime and purpose |
|---|---|---|
@openagentid/sdk | 0.7.2 | Node 20+; identity, verification, OATS, characters and browser player |
create-openagent | 0.5.2 | Node 20+; complete local application |
@openagentid/oidc | 0.2.0 | Node 20.19+; agent OIDC issuer and federation |
openagentid-sdk on PyPI | 0.1.0 | Python 3.10+; separate ACT, key and middleware APIs |
Begin with the quickstart, TypeScript SDK or CLI tools. The Node path includes persistent real keys, explicit trust and live avatars without a Life account or hosted identity service.
Component packages
The npm reference lists each published package's exact version, export paths, dependency ranges and declarations. OAS components publish independently at 1.0.2; Arsenal, AEGIS, skills, transport and framework packages have their own releases. Installing the latest SDK does not upgrade these separate contracts.
In particular, @openagentid/mcp, @openagentid/claude-agent, @openagentid/scim and @openagentid/sdk-testing 0.1.1 declare SDK ^0.1.0 peers. That range does not include SDK 0.7.2. Their references are compatibility material, not a supported current-starter combination.
Other languages
| Implementation | Availability and reference |
|---|---|
| Rust | Published component crates and source-only facade |
| Python | Public PyPI 0.1.0 and its API boundaries |
| Go | Source integration status |
| Swift | Source integration status |
| Kotlin | Source integration status |
Languages have independent APIs, dependencies and release schedules. TypeScript local-workspace and avatar support does not imply feature parity elsewhere. ACT byte-format interoperability also does not imply cross-language encryption-key recovery, session interchangeability or a configured production issuer.