Tempo MPP Go SDK

Why it's ranked here

The design covers both sides of a paid HTTP exchange and fits established Go server stacks. Strict header parsing, payload size limits, constant-time comparisons, structured errors, split validation and settlement, and several complete payment examples show attention to operational details. It is compelling for MPP adoption, but tightly focused on this protocol and Tempo charge flows.

What's good

The SDK separates generic protocol types, HTTP client behavior, server verification, and Tempo-specific settlement. It supports standard HTTP directly, needs no special Chi adapter, and includes dedicated Gin, Echo, and Fiber integrations. Paid POST guidance correctly treats an external identifier as receipt metadata, not durable idempotency. Validation can also remain advisory until a separate broadcast step performs settlement.

Tradeoffs

Applications must persist idempotency records or cached responses themselves before executing paid side effects. The split lifecycle still revalidates during settlement, and validation requires intents configured with separate hooks. Tempo usage introduces blockchain, RPC, key, recipient, replay, and possible relay concerns beyond ordinary HTTP middleware. The dependency graph also includes several web frameworks, Redis, Ethereum tooling, and Tempo libraries.

How to use it well

Use it when a Go client must purchase an HTTP response, or when a Go service must charge per request using MPP and Tempo. Start with the generic client and server layers, then select standard HTTP or the matching framework adapter. For paid mutations, pair stable client idempotency values with application-owned storage. It does not provide billing accounts, checkout pages, or durable business-operation deduplication.

Observed

License

Dual licensed under MIT or Apache License 2.0, at the user's option.

Primary language

Go.

Packaging

Go module published as github.com/tempoxyz/mpp-go.

Install surface

Installed with go get github.com/tempoxyz/mpp-go.

Interface

Library packages provide an HTTP 402 client transport, server middleware, protocol types, and Tempo charge support.

Framework support

Supports standard net/http and Chi interfaces, plus dedicated Gin, Echo, and Fiber adapters.

Testing surface

The Makefile defines unit, coverage, formatting, vet, module verification, and tagged integration test targets.