Other languages

Go SDK — not implemented

sdk/go/ is a placeholder. Planned surface, to be built against api/ROUTES.md and the event schema, byte-for-byte aligned with the Go core's own internal/core/event.Event:

Client.Emit(ctx, EventInput) (Event, error)                       // wraps POST /v1/events
Client.ServeWithProof(ctx, subject, docID) (token string, err error) // local render-token mint
Client.Feed(ctx, FeedQuery) (PageResult, error)                    // wraps GET /v1/feed

A Go SDK is the natural place for a first-class ServiceMinter-backed helper, closing the service-token minting gap the TypeScript SDK currently has — Go backends can already use internal/core/trust.ServiceMinter directly today without waiting for a packaged SDK, since it lives in the same module.

Python SDK — not implemented

sdk/py/ is a placeholder, aimed at backend frameworks (e.g. a typical FastAPI service) that want to emit events and mint render-tokens for content they serve:

Client.emit(event_type, target=..., data=..., ...) -> Event
Client.serve_with_proof(subject, doc_id) -> str        # local render-token mint helper
Client.feed(subject_id, filter=..., page=...) -> PageResult

Until either lands

Any backend, in any language, can integrate against CNS today with plain HTTP: API Reference → Data plane has the complete request/response shapes for every route, and Trust & render-tokens documents the render-token's exact claim shape (standard JWT/EdDSA — mintable with any competent JWT library) if you need to mint one outside Go or TypeScript.