Why use this instead of a plain HttpClient POST?

It uses source-generated System.Text.Json for reflection-free serialization, described as AOT and trim safe with lower allocations and startup cost.

Do I need to manage HttpClient lifetime myself?

Yes. The digest instructs passing a pooled client such as from IHttpClientFactory to avoid socket exhaustion; the client is thread-safe and meant to be reused.

What happens on rate limiting or overload responses?

Retriable 429 and 529 responses are retried with exponential backoff plus jitter honoring Retry-After; other non-success responses throw TypeSafeApiException.

Can state be structured data instead of a string?

State and Instructions accept JsonNode, so assign a string directly or a JsonObject or JsonArray for structured state and criteria.

What platform does it target, and how is it built?

It is a .NET 10 client for the TypeSafe evaluation API at POST /v1/systemone, using source-generated System.Text.Json for reflection-free serialization that is AOT and trim safe, with streamed request and response bodies that are never buffered into intermediate strings.

What does the answer surface look like?

NoulQuestion returns a NoulAnswer with a Noul value from 0 to 1; ChoiceQuestion returns Choice, Probabilities and Confidence; and ScoreQuestion returns Score, Legend, Probabilities and Confidence. Answers are cast from a dictionary, for example (NoulAnswer)response.Answers["is_urgent"].

How are failures surfaced?

Non-success responses throw a TypeSafeApiException carrying StatusCode and ResponseBody, after automatic retries for 429 and 529 responses with exponential backoff and jitter that honours a Retry-After header.

CommunityJev Benchmarks & Evaluations

TypeSafe AI Lib

.NET 10 client for the TypeSafe evaluation API that evaluates a state against typed questions and returns structured answers.

See highlights

Open github.com

Stars: 0
Language: C#
Published by: Community
Author: timdinh
Last verified: Oct 2026

timdinh/typesafe-ai-lib

User repository on GitHub

View on GitHub

High-performance .NET client for the TypeSafe evaluation API (POST /v1/systemone), compatible with the native API and the Vercel AI Gateway. Source-generated JSON, streaming bodies, automatic 429/529 retries

Forks: 0
Last pushed: Updated Sep 2026

Repo stats from the GitHub API, cached Oct 2026.

About this project

A high-performance .NET 10 client library for the TypeSafe evaluation API (POST /v1/systemone). Evaluate a state against typed questions and get back structured answers. Source-generated System.Text.Json — reflection-free serialization; AOT/trim safe, lower allocations and startup cost. Streaming bodies — request and response JSON are streamed (ResponseHeadersRead), never buffered into intermediate strings.

Quoted from the project's README. Read the full README.

Tagscommunity github

Works forJev for Evaluation

Used inJev for Software & DevTools

Languages: C# / .NET

Highlights

Targets POST /v1/systemone with Noul, Choice, and Score question and answer types.
Streams request and response bodies with ResponseHeadersRead instead of buffering strings.
Retries 429 and 529 with exponential backoff plus jitter honoring Retry-After.
Throws TypeSafeApiException with StatusCode and ResponseBody after retries are exhausted.

Watch out

Client library only; request shape and model behavior still follow the TypeSafe evaluation API. 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.

More Jev resources like this

jev-evals

Rubric-based eval harness that judges LLM and agent outputs with Jev through the Vercel AI Gateway, answering all rubrics for a case in one round trip.