What it does
Generated question sets avoid runtime reflection, but a complete request still allocates memory. The speed comparisons use local mocks, not live inference.
SDKs & clients
Declare Jev questions as C# types, then try routing, guardrails and search ranking with saved answers before making live calls.
Only you can see your notes.
Screenshot unavailable. Open the experiment ↗
Generated question sets avoid runtime reflection, but a complete request still allocates memory. The speed comparisons use local mocks, not live inference.
Ask a developer to study the travel-request example when planning a support service. It chooses between finding a booking, asking an assistant and involving a person. Uncertain cases go to the person. The example prints those choices; it does not connect them to a real booking system.
Use the saved answers first: they let you check your program without paying for new AI answers. Trying new messages instead sends them to a paid outside service through OpenRouter. This only tests the idea; it does not supply a working booking service. Package publication is not confirmed, so start with the repository examples.