A strong candidate for transport services and event-heavy workloads. Go SDK

For infrastructure services, event pipelines, and high-throughput implementations.

The Go SDK fits execution backends and protocol services that value straightforward concurrency, stable contracts, and operational simplicity.

Back to SDKs Read roadmap

What this page covers

Keep wire contracts explicit.

Design for replayable events.

Separate transport concerns from protocol semantics.

Use extensions conservatively.

Highlights

Protocol-native entry points for this surface.

Service-friendly

Well suited for protocol APIs, event relays, and backend workers.

See reference services

Concurrent flows

Useful when many mission activities and evidence streams run in parallel.

See lifecycle

Predictable contracts

Stable types and payload shapes matter for interoperable infrastructure.

Read spec

mission, _ := client.Missions.Create(ctx, payload)
client.Evidence.Attach(ctx, mission.ID, evidence)
verification, _ := client.Verifications.Evaluate(ctx, mission.ID)

Working principles

Keep the protocol stable while implementations evolve.

Keep wire contracts explicit.

Design for replayable events.

Separate transport concerns from protocol semantics.

Use extensions conservatively.

SDK overview

Compare language surfaces while preserving the same protocol core.

Open overview

Roadmap

Track where official SDK support is headed next.

See roadmap

Next step

Build boring, durable infrastructure.

The protocol should remain stable while implementations scale. Go is a good fit for those lower-level protocol services.