Overview

Genesis Mesh ships client libraries for all major server-side runtimes. Every SDK wraps the same Network Authority HTTP API — the surface documented in Trust API — HTTP Reference.

SDKs are standalone packages: they live in separate repos under C:\Source\GenesisMeshLabs\sdk-*\ and are not part of the Python main repo. They share no runtime dependencies with the Python server.

Available

SDK	Package	Version	Repo
TypeScript / Node.js	genesis-mesh-sdk on npm	0.53.0	sdk-typescript/
Go	github.com/GenesisMeshLabs/sdk-go	0.54.0	sdk-go/
C# / .NET	genesismesh-sdk-dotnet on NuGet	0.55.0	sdk-dotnet/

Design principles

All SDKs mirror the main repo’s layer separation:

Layer	TypeScript	Go	C#	Python equivalent
Crypto	src/auth.ts	genesismesh/auth.go	Auth.cs	genesis_mesh/crypto/
HTTP transport	src/client.ts	genesismesh/transport.go	Transport.cs	na_service/
Domain sub-clients	src/agreement.ts …	genesismesh/agreement.go …	Clients/*.cs	na_service/routes/
Types	src/types.ts	genesismesh/types.go	Models.cs	genesis_mesh/models/

No runtime dependencies. SDKs use only the platform’s built-in fetch and crypto APIs.

Typed errors. Every HTTP error is mapped to a typed exception class (BadRequestError, UnauthorizedError, ValidationError, etc.) with a stable .code string matching the NA’s code field.

Dual-mode auth. Admin routes are signed with Ed25519 (four X-Admin-* headers). Public verification routes are unauthenticated. The transport layer handles the distinction — callers just use the right sub-client method.