User repository on GitHub
TypeSafe.ai Jev Go SDK
- Forks
- 0
- Last pushed
- Updated Sep 2026
Repo stats from the GitHub API, cached Oct 2026.Homepage
CommunityJev Repos & SDKs
Jev Go — kyledickey
Small Go SDK for the Jev API: three question types with matching typed answers, functional client options, and a single APIError type carrying the status code, headers and raw body.
- Stars
- 1
- Language
- Go
- License
- MIT
- Published by
- Community
- Author
- kyledickey
- Last verified
- Oct 2026
This is one of several Jev listings for the same project. The canonical entry is Jev Go — Stumble.
About this project
A Go SDK for TypeSafe's Jev API. The client reads your key from TYPESAFEAPIKEY by default. There are three question types, each with a matching answer type: See the Jev docs for how each one works, and examples/basic for a full program. Non-2xx responses come back as jev.APIError, which has the status code, headers, and raw body. Requests aren't retried, so wrap calls yourself if you need that.
Quoted from the project's README. Read the full README.
Works forJev for Classification
Used inJev for Software & DevTools
- Languages
- Go
Highlights
- Package name is jev, and the client reads TYPESAFE_API_KEY by default or takes it through WithAPIKey.
- NoulQuestion, ChoiceQuestion and ScoreQuestion each pair with a typed answer reached through a type assertion.
- Non-2xx responses come back as *jev.APIError with the status code, headers and raw body attached.
- A full program lives in examples/basic, and CI runs the same gofmt, go vet and go test -race checks.
Watch out
Requests are not retried at all, so any resilience has to be wrapped around the client by the caller. Beyond passing your own *http.Client through WithHTTPClient there is no documented timeout knob, and no per-call model override is shown. The base URL in the options example includes /v1, which is worth checking against the current API docs since other TypeSafe clients expect the API root without it. Which version of the API the client tracks is not stated. 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. The README says plainly that requests aren't retried and that you should wrap calls yourself if you need that. That makes the client small and predictable, but it also means timeouts, backoff and idempotency concerns are entirely yours. Non-2xx responses surface as *jev.APIError, which you can match with errors.As and read StatusCode and Body off.
Answers come back keyed by the question name you used, and you assert the concrete type. For a noul question the check is a type assertion to *jev.NoulAnswer and you read the probability off the Noul field; the same pattern applies to *jev.ChoiceAnswer and *jev.ScoreAnswer. The example in the README ends with an ok check rather than a panic, so a missing key or unexpected type is a branch you handle.
go get github.com/kyledickey/jev-go, and the package name is jev rather than typesafe. The key comes from TYPESAFE_API_KEY by default, or you pass WithAPIKey, and you can also set WithHTTPClient and WithBaseURL. For how each question type actually behaves the README defers to the official Jev primitives docs rather than restating them.
It is a separate, smaller one. This client exposes only client construction, SystemOne, the three question and answer type pairs, functional options and one error type, with no retry, logging or unknown-field handling documented. If you need retries with Retry-After handling and slog diagnostics, that is a different SDK.
Non-2xx responses come back as a *jev.APIError carrying the status code, headers and raw body, which you can inspect with errors.As; requests are not retried, so wrap calls yourself.
WithAPIKey, WithHTTPClient for a custom timeout and WithBaseURL; the client reads TYPESAFE_API_KEY by default and returns a typed answer per question type.
gofmt -l ., go vet ./... and go test -race ./..., the same set CI runs; issues and PRs are welcome and a bigger change is worth an issue first.
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-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/jevgoGoFrom 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.