SDK & Language Compatibility Matrix

1. Scope

This document defines the feature-level compatibility status of H33 SDK bindings across programming languages, AI frameworks, and orchestration platforms. Five feature categories are evaluated per platform: agent attestation, tool wrapping, memory checkpoints, deterministic replay, and independent verification.

SDKs are distributed through the H33 GitHub organization. All SDKs communicate with the H33 API backend; cryptographic operations (signing, FHE, ZKP) execute server-side. SDK bindings handle serialization, transport, receipt parsing, and local verification of attestation receipts.

2. Feature Definitions

Agent Attestation

Per-action cryptographic attestation of AI agent operations. Each tool invocation, LLM call, or decision point produces an H33-74 attestation primitive bound to the agent's session.

Tool Wrapping

Automatic instrumentation of agent tool calls. The SDK intercepts tool function invocations, captures inputs and outputs, and generates attestation receipts without requiring changes to the tool implementation.

Memory Checkpoints

Periodic attestation of agent memory state. The SDK hashes the agent's context window, working memory, or vector store at configurable intervals and produces an attestation receipt binding the memory state to a point in time.

Deterministic Replay

Reconstruction of an agent session from its attestation receipt chain. Given a sequence of receipts, the replay engine re-executes the session and verifies that each output matches the attested output.

Independent Verification

Local verification of attestation receipts without contacting the H33 API. The SDK includes the three public keys and verification logic necessary to validate receipt signatures, chain integrity, and H33-74 primitive structure.

3. Status Designations

Available

The feature is implemented, tested, published, and supported. It is available through the official package registry (npm, PyPI, crates.io, pkg.go.dev).

Planned

The feature is committed to the roadmap. The SDK architecture supports it but the implementation is not yet published.

Community

A community-maintained integration exists. H33 does not provide official support, testing, or compatibility guarantees for community bindings.

N/A

The feature is not applicable to this platform (e.g., memory checkpoints are not meaningful for a stateless verification CLI).

4. Primary Compatibility Matrix

Platform	Agent Attestation	Tool Wrapping	Memory Checkpoints	Replay	Verification
TypeScript @h33/agent	Available	Available	Available	Available	Available
Python h33-agent	Available	Available	Available	Available	Available
Rust h33-agent	Available	Available	Available	Available	Available
Go h33-agent-go	Planned	Planned	Planned	Planned	Planned
MCP @h33/mcp	Available	Available	Available	Available	Available
LangChain h33-langchain	Available	Available	Planned	Planned	Available
OpenAI h33-openai	Available	Available	Planned	Planned	Available
CrewAI h33-crewai	Planned	Planned	Planned	Planned	Community
Vercel AI h33-vercel-ai	Planned	Planned	Planned	Planned	Community

5. SDK Architecture

5.1. Core SDKs (TypeScript, Python, Rust)

The three core SDKs provide full feature coverage. They share an identical wire protocol and produce interoperable attestation receipts. A receipt generated by the TypeScript SDK can be verified by the Rust SDK and vice versa.

Core SDKs implement receipt verification locally. The three post-quantum public keys are bundled in the SDK package, and all signature verification (ML-DSA-65, FALCON-512, SLH-DSA-SHA2-128f) is performed client-side without network calls. This enables offline verification workflows and air-gapped environments.

The Rust SDK is the reference implementation. TypeScript and Python SDKs use a Rust sidecar for cryptographic operations via FFI (TypeScript: N-API; Python: PyO3). Application-level logic (serialization, transport, receipt parsing) is implemented natively in each language.

5.2. MCP SDK

The MCP SDK implements the Model Context Protocol with H33 attestation instrumentation. Every MCP tool call is automatically wrapped with an attestation receipt. The SDK integrates with any MCP-compatible client (Claude Desktop, Cursor, custom MCP hosts) without requiring client-side modifications.

MCP tool wrapping operates at the protocol transport layer. The SDK intercepts JSON-RPC messages between client and server, generates attestation receipts for each tool invocation, and appends receipt references to the response metadata. The client receives unmodified tool outputs; attestation is transparent.

5.3. Framework Integrations (LangChain, OpenAI)

Framework integrations provide agent attestation and tool wrapping through framework-native extension points. For LangChain, this is the callback handler interface. For OpenAI, this is the function calling wrapper.

Framework integrations depend on the Python core SDK (h33-agent) as a transitive dependency. They do not re-implement cryptographic operations. Memory checkpoints and replay are planned for a future release pending framework-specific memory abstraction APIs.

5.4. Go SDK

The Go SDK is in active development. It will use cgo bindings to the Rust cryptographic core. Target release: Q3 2026. The Go SDK will provide full feature parity with the TypeScript, Python, and Rust SDKs upon release.

5.5. Community Integrations (CrewAI, Vercel AI)

Community integrations are maintained by third-party developers. H33 provides technical guidance and conformance test vectors but does not guarantee compatibility, security, or API stability for community bindings. Community integrations are tested against the HATS Conformance Suite and receive a compatibility badge upon passing.

6. Package Registry Reference

Package	Registry	Language	Install Command
@h33/agent	npm	TypeScript	npm install @h33/agent
h33-agent	PyPI	Python	pip install h33-agent
h33-agent	crates.io	Rust	cargo add h33-agent
@h33/mcp	npm	TypeScript	npm install @h33/mcp
h33-langchain	PyPI	Python	pip install h33-langchain
h33-openai	PyPI	Python	pip install h33-openai

7. Conformance Requirements

SDKs claiming compatibility with the H33 attestation protocol must satisfy the following:

1. Produce valid H33-74 attestation primitives conforming to the H33-74 Specification.
2. Verify all three post-quantum signatures (ML-DSA-65, FALCON-512, SLH-DSA-SHA2-128f) during receipt verification.
3. Validate evidence chain integrity by checking predecessor hashes.
4. Pass all test vectors in the HATS Agent Conformance Vector Suite v1.
5. Implement structured error reporting with H33-74 failure codes.

Community SDKs may request conformance evaluation by submitting test results to the HATS conformance program.