Organization repository on GitHub
A Go SDK for the TypeSafe API, enabling quick integration with Jev.
- Forks
- 0
- Last pushed
- Updated Sep 2026
Repo stats from the GitHub API, cached Oct 2026.
CommunityJev Repos & SDKs
TypeSafe SDK Go — unimtx
Community Go client for the TypeSafe API: context-aware SystemOne calls, Choice, Noul and Score constructors, scoped functional options, typed errors carrying RFC 6901 field paths, and standard-library-only runtime code. Requires Go 1.24.
- Stars
- 1
- Language
- Go
- License
- MIT
- Published by
- Community
- Author
- unimtx
- Last verified
- Oct 2026
This is one of several Jev listings for the same project. The canonical entry is TypeSafe SDK Go — Tangerg.
About this project
A community-maintained Go SDK for the TypeSafe HTTP API, built to fill the gap left by the absence of an official Go SDK and enable quick integration with Jev, a System One model. This project is unaffiliated with and not endorsed by TypeSafe. The API favors normal Go conventions: contexts, keyed structs, scoped functional options, concrete errors, and standard net/http interoperability. Runtime code uses only the Go standard library. The minimum supported version is Go 1.24.0.
Quoted from the project's README. Read the full README.
Used inJev for Software & DevTools
- Languages
- Go
Highlights
- Questions are validated before the request leaves: non-empty IDs, Choice 1–255 options, Score 2–10 ordered levels, Noul needing instructions or criteria.
- Typed errors separate caller cancellation from SDK timeouts: timeout, API and response-validation types, plus sentinels for connection and rate limits.
- Retries twice by default after connection failures, timeouts and 408/429/5xx, reusing the same serialized body with backoff from 500 ms to 5 s plus jitter.
- Choice returns the full probability distribution and a confidence summary; Noul returns a probability of yes with no confidence, so the threshold is yours.
Watch out
Community-maintained and explicitly unaffiliated with TypeSafe, so there is no official support contract behind it, and the minimum Go version is 1.24.0. Retries are on by default and there is no total retry budget: a lost response can mean the evaluation runs again and you are billed twice, so bound the whole call with a context deadline and disable retries where duplicate usage is unacceptable. Question IDs are wire and lookup keys only — the model never sees them — so the judgment has to live in the instructions, which is easy to get wrong when porting from another SDK. The examples call the live API and can cost you; the ordinary test suite stays offline. 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.
It is a community-maintained client written because there was no official Go SDK, and the README states plainly that it is unaffiliated with and not endorsed by TypeSafe. Runtime code is standard library only and it interoperates with net/http, so the surface is small, but nothing here promises compatibility tracking against a future API revision.
Possibly, and the README says so directly: a lost response can cause a repeated evaluation and duplicate usage. Two retries by default follow connection failures, per-attempt timeouts and 408, 429 and 5xx responses, and there is no total retry budget — you bound the whole call with a context deadline and, where duplicate charges matter, set the max-retries option to zero for that request.
No. IDs are wire keys and response lookup keys, and the README is explicit that the model does not use them for inference. The whole judgment has to sit in the instructions, with criteria entries carrying the detail. If you name a question tone and leave its instructions empty, you have handed the model a word and no question.
By error type. Caller cancellation and deadline expiry match context.Canceled and context.DeadlineExceeded, also match the user-abort sentinel, and are never retried; an SDK per-attempt timeout comes back as a TimeoutError, which matches both the timeout and connection sentinels. That distinction is what lets you stop retrying work the caller no longer wants.
Yes. The client rejects invalid question shapes before sending: IDs must be nonempty, Choice accepts one to 255 options, Score accepts two to ten ordered levels, and Noul needs non-null instructions or at least one non-null true/false description. Catching those locally avoids a wasted round trip to a metered endpoint.
Timeout, retries and headers can be overridden per request; the API key, base URL, default model, HTTP client, logger and log level are client-only. Explicit options also override TYPESAFE_API_KEY, TYPESAFE_BASE_URL, TYPESAFE_DEFAULT_MODEL and TYPESAFE_LOG_LEVEL. Default retry backoff starts at 500 ms, doubles to five seconds and subtracts up to 25 percent jitter.
Go 1.24.0 is the minimum supported version, and runtime code uses only the standard library. It favors ordinary Go conventions: contexts, keyed structs, scoped functional options, concrete errors and standard net/http interoperability. The ordinary test suite stays offline; only the examples call the live API and may incur usage.
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-goGo8GitHub stars
Unofficial Go client for the TypeSafe System One API that sends a state plus typed Noul, Choice, and Score questions in one call and returns typed answers with model, usage, and request ID.
Jev Repos & SDKs#community#awesomejev#catalog-import
Community
devbackend/jevgoGo
devbackend/jevgoGo4GitHub 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-goGo5GitHub stars
Zero-dependency Node bridge that exposes Jev through OpenAI-style chat and responses endpoints with streaming, plus a CLI, a code-audit tool, and an auto-fix loop.
Jev Repos & SDKs#community#awesomejev#catalog-import
1GitHub 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-goGoFrom 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.