Question 1

Do the enum and typed-response helpers survive a Native AOT publish?

Accepted Answer

They are built for it. Typed responses derive from SystemOneResponse and fill each property from the answer of the same name, matching exactly, then case-insensitively, then snake_case. Optional answers are marked with [OptionalAnswer] rather than inferred from nullability, because the trimmer removes that metadata and inference would make the same class validate differently in a Native AOT build. JsonContent.From takes a JsonTypeInfo<T> when you serialize your own state. The repo publishes and runs a native binary on every build, and CI fails if the packed .nuspec grows a second dependency.

Question 2

What does this save me over calling the API with a plain HttpClient?

Accepted Answer

Mostly the parts you would otherwise assemble: retries that match the official SDKs on 408, 429 and 5xx with jittered backoff, Retry-After handling, per-attempt timeouts and a budget for the whole call, without pulling in Polly. Logging and OpenTelemetry come through ILogger, ActivitySource and Meter rather than extra packages, and you get the enum and typed-response mapping. If you already have an HttpClient pipeline that does all of that, the remaining argument is the typing and the one-dependency, AOT-safe package.

Question 3

Are the confidence and probability numbers calibrated, or raw model output?

Accepted Answer

The README does not claim calibration and does not report any measurement, so treat them as what the API returns. What it does document is the shape: a Noul answer is a probability from 0 to 1 where something near 0.5 means the model cannot tell, a Choice answer carries a confidence plus the probability of every option so you can see when second place was close, and a Score answer is the probability-weighted average across the rubric, which is why 1.7 reads as mostly level 2 pulled towards level 1. Set your own threshold on top, and route the rest to a human.

Question 4

What happens when the model returns something my code does not model?

Accepted Answer

You get an exception rather than a wrong default. As<TEnum>() throws JevResponseValidationException if the API returns a name that is not an enum member, which the README argues beats a silently wrong default, and asking for the wrong answer type or for a name that was never in the request throws the same exception instead of returning null. The response also carries res.Model, the exact version that answered, res.Usage token counts and res.RequestId, which maps to the x-typesafe-request-id header for support.

Question 5

What does it target and how do I install it?

Accepted Answer

net8.0, net9.0 and net10.0 with C# 12 or later. Install with dotnet add package TypeSafe.Jev and supply TYPESAFE_API_KEY from typesafe.ai.

Question 6

Does it bring its own retry policy?

Accepted Answer

Yes. It retries 408, 429 and 5xx with jittered backoff and Retry-After, plus per-attempt timeouts and a budget for the whole call, matching the official SDKs and without pulling in Polly.

Question 7

How are enum members sent and returned?

Accepted Answer

Member names travel as snake_case, so TechnicalIssue becomes technical_issue, and [Description] becomes the option's rubric; without one the option is sent with an explicit null, and As<TEnum>() throws if the API returns a non-member.

TypeSafe.Jev

About this project

Highlights

Questions about this entry

More Jev resources like this

From the Jev guides

From the Jev community