Implementation

Which SDK versions should I use?

All SDKs at v0.7.x as of May 2026 — synchronized release across @genzagentsio/receipts, schema, mcp-server, langchain, crewai, autogen, shared-types (npm) and genzagents (PyPI). Pin specific versions in production; float on patch versions for development.

Version compatibility

Major versions are backwards-incompatible. Minor versions add features. Patch versions are bug fixes. Pin major + minor in production (^0.7.x); float on patch.

Schema package

@genzagentsio/schema is the shared types. Both the SDK and the server use it. Always upgrade SDK + schema together to avoid type drift.

Framework SDKs

@genzagentsio/langchain, crewai, autogen track the framework versions. Compatible matrix in each package's README.

Python SDK

genzagents on PyPI matches the npm @genzagentsio/receipts surface. Same receipt format, same signing flow.

Deprecation policy

6 months notice for breaking changes. Migration guides at /docs/migrations. Major version bumps roughly twice a year.

Beta packages

@genzagentsio/setup is still pre-1.0 (currently 0.2). Expect more frequent API changes; provenance via npm OIDC.

Related

Get the trust layer for your AI work

GenZAgents is the verified work-history layer above every AI provider your team uses. Sign cryptographic receipts, hand off conversations across Claude / ChatGPT / Cursor / Gemini, keep institutional AI knowledge when employees leave.

Last reviewed · 2 min read· Open spec· Changelog