User repository on GitHub
Idiomatic Go SDK for the TypeSafe AI API
- Forks
- 0
- Last pushed
- Updated Oct 2026
Repo stats from the GitHub API, cached Oct 2026.Homepage
CommunityJev Repos & SDKs
TypeSafe Go — zhirschtritt
An unofficial, dependency-free Go client for the TypeSafe v1 API: System One calls built from Noul, Choice and Score questions, per-request model overrides, typed answers with a request ID, and retries that honor Retry-After.
- Stars
- 3
- Language
- Go
- License
- MIT
- Published by
- Community
- Author
- zhirschtritt
- Last verified
- Oct 2026
This is one of several Jev listings for the same project. The canonical entry is TypeSafe Go — sd109.
About this project
An unofficial community SDK for the TypeSafe v1 API. It provides a small, dependency-free Go client for System One and model discovery. Use client options to configure a key, base URL, default model, retry behavior, HTTP transport, and maximum response size. Request options can override request-scoped settings such as the model without mutating the client.
Quoted from the project's README. Read the full README.
Works forJev for Classification
Used inJev for Software & DevTools
- Languages
- Go
Highlights
- Question helpers map onto the three decision types: Noul for a yes-or-no, Choice over a map of entries, Score over ordered labels.
- Retries honor server Retry-After headers and never retry a canceled context, and every successful response exposes a RequestID.
- Unknown answer types survive decoding as *typesafe.UnknownAnswer with their raw JSON, so a newer server does not silently drop data.
- Versions come from Conventional Commits through Release Please, so a `!` marker or a BREAKING CHANGE footer is what cuts a major tag.
Watch out
The README states plainly that this is an unofficial community SDK, not affiliated with or endorsed by TypeSafe, and points at the official JavaScript and Python SDKs as the reference implementations. Coverage is System One plus model discovery rather than the whole API, and the Go minimum is 1.23, which rules out the generic concrete methods and generic question constructors the project lists as future work. The version string sent in request headers is maintained by the release pull request, not a hand-edited file, and there is no changelog file to read instead. Forward compatibility is real but not free: an answer type newer than the SDK arrives as UnknownAnswer and you have to handle it explicitly. Copy reviewed against the repository README on 2026-10-04, not from running it.
Questions about this entry
Short answers drawn from the linked project or page.
No on both counts, and the README does not hedge. It describes the project as an unofficial community SDK, carries a line saying it is not affiliated with or endorsed by TypeSafe, and lists TypeSafe's official JavaScript and Python SDKs plus the public OpenAPI specification under References. Security issues go to the address in SECURITY.md rather than to a vendor support channel.
System One and model discovery, as the README's one-line summary puts it. Configuration is three environment variables: TYPESAFE_API_KEY, TYPESAFE_BASE_URL and TYPESAFE_DEFAULT_MODEL, and everything else is client options for retry behavior, HTTP transport and maximum response size, with request options overriding request-scoped settings such as the model without mutating the client. Releasing is Conventional Commits through Release Please: fix gives a patch, feat a minor, and a `!` or a BREAKING CHANGE footer a major.
You get it, not an error and not a silent drop. The decoder accepts additive JSON fields, and an answer type newer than the SDK is preserved as a *typesafe.UnknownAnswer carrying its raw JSON. The README is direct that you need to handle it explicitly when consuming evolving responses, so the forward compatibility buys you data rather than correctness.
Not at Go 1.23, the current minimum. The future-improvements section lists generic concrete methods for Client.SystemOne and generic question constructors as work to do when Go 1.27 is an acceptable minimum, so that each call keeps its concrete state and instruction types until JSON encoding while one client still accepts different types across calls. The same note points out that JSON compatibility would still need runtime validation, because an `any` constraint cannot exclude values encoding/json does not support.
go get github.com/zhirschtritt/typesafe-go, requiring Go 1.23 or later, and it has no dependencies. Configuration is three environment variables, TYPESAFE_API_KEY, TYPESAFE_BASE_URL and TYPESAFE_DEFAULT_MODEL, plus client options for the key, base URL, default model, retry behavior, HTTP transport and maximum response size. Request options can override request-scoped settings such as the model without mutating the client.
Transient failures follow the configured retry policy, it honors server Retry-After responses, and it never retries a canceled context. Every successful response exposes a RequestID, and typed HTTP errors carry the status, headers, request ID and a bounded response body for diagnostics.
Semantic Versioning driven by Conventional Commits through Release Please: fix gives a patch, feat a minor, and a `!` marker or a BREAKING CHANGE footer a major. After CI passes on main, Release Please opens a release pull request; merging it creates the tag and GitHub Release, and it also updates the Version string sent in SDK request headers. There is no changelog file to read instead.
More Jev resources like this
45GitHub stars
Go SDK plus a pipeline-friendly CLI for typed decisions, covering single questions, batched question maps, retries, and line-oriented filtering over stdin.
Jev Repos & SDKs#community#jevbest#catalog-import
Community
mattn/go-jevGo
mattn/go-jevGo9GitHub stars
Go SDK for the TypeSafe API that asks typed Noul, Choice, and Score questions about a state and returns probability distributions with confidence and typed accessors.
Jev Repos & SDKs#community#jevbest#catalog-import
Community
Tangerg/typesafe-sdk-goGo
Tangerg/typesafe-sdk-goGo4GitHub stars
Community Go client for the TypeSafe System One evaluation API with raw structs and a builder that produce the same EvaluationRequest, defaulting to jev-latest.
Jev Repos & SDKs#community#jevbest#catalog-import
Community
kisshan13/typesafe-ai-goGo
kisshan13/typesafe-ai-goGo1GitHub stars
Unofficial, independently maintained Go client for the TypeSafe AI System One API with no third-party dependencies: choice, score and noul questions, typed accessors that error instead of returning zero, and per-call timeout, retry and header overrides.
Jev Repos & SDKs#community#jevbest#catalog-import
Community
cole-gillespie/typesafe-goGo
cole-gillespie/typesafe-goGo2GitHub stars
Community Go client for the TypeSafe AI System One API covering the same surface as the official Python and TypeScript SDKs, using functional options, context cancellation, sentinel errors, `log/slog`, no dependencies outside the standard library, and optional Langfuse tracing.
Jev Repos & SDKs#community#jevbest#catalog-import
Community
fgn/jevgoGo
fgn/jevgoGo1GitHub stars
An unofficial Go client that keeps Jev answers in your own types, so a choice over your enum yields that enum and the compiler checks the switch you write on it.
Jev Repos & SDKs#community#jevbest#catalog-import
Community
anilsenay/jevGo
anilsenay/jevGoFrom the Jev guides
Original write-ups on what this entry is for.
Closed weights have not stopped the ecosystem from rebuilding the shape in the open. API-compatible servers, retrained heads on small models, and inference-time tricks that skip generation entirely.
Jev Repos & SDKs#open-models#research#local
Read article
From the Jev community
Posts from builders shipping with Jev right now.