Question 1

How much of this is the official SDK and how much is the community edition?

Accepted Answer

The core is a port with the same primitives, wire format, retry behavior, and error semantics as the official Python SDK. What the community edition adds is derive macros, typed function calling, weighted composite scoring, decision helpers, a mock transport, a response cache, and an evaluation harness.

Question 2

Do I need to depend on both crates, and what breaks if I rename the dependency?

Accepted Answer

You add one crate; the proc-macro crate is a dependency whose derives are re-exported under the default derive feature. If you rename it in Cargo.toml, the derives need to be pointed at the new name with the crate attribute on choice, score, or questions, or the macros will not resolve.

Question 3

Can I run its tests without an API key?

Accepted Answer

Yes. A mock transport with generated fixtures keeps the suite offline, and live tests skip themselves when TYPESAFE_API_KEY is absent. Turning off default features drops the derives, but the traits in the typed module can still be implemented by hand.

Question 4

What Rust version does it require, and who fixes it when the API changes?

Accepted Answer

Rust 1.88 or newer. Maintenance is the catch: it is an independent community port, explicitly not maintained by TypeSafe, and published under a -community crate name rather than the official one, so this repository is what has to catch up when the wire format moves.

Question 5

What do the derive macros catch at compile time?

Accepted Answer

Questions turns a struct into a whole question set, while ChoiceLabels and ScoreLevels turn enums into choice labels or a score rubric. A misspelled label is a compile error, and so is putting a choice attribute on a noul-shaped field. Field types pick what you get back: NoulAnswer, bool or f64 for a noul, ChoiceAnswer or TypedChoice<T> for a choice, and Option of any of them to tolerate a missing answer.

Question 6

What does Route give me over a plain choice question?

Accepted Answer

It is typed function calling. One choice question selects a variant, and every variant's fields are questions too, all sent in the same request, so you pay for the speculative fan-out and only the winning variant is constructed. send_full() returns a Routed<Intent> carrying the routing ChoiceAnswer with its confidence, margin and every variant's probability, so an uncertain route can be gated like any other choice.

Question 7

How do I turn probabilities into an action?

Accepted Answer

With the decision module, where the thresholds are yours. Bands::new(0.3, 0.7) on a noul returns Yes, No or Uncertain, and Gate::new(0.85, 0.6) on a choice returns Accept, Review or Reject. Choices also expose margin(), top(n), entropy() and normalized_entropy(); scores expose probability_at_least(level), std_dev() and normalized(); nouls expose certainty(), and an evaluation harness ships for choosing thresholds on your own data.

TypeSafe AI Rust SDK (community)

About this project

Highlights

Quickstart

Questions about this entry

Reactions & coverage

From the Jev guides

From the Jev AI model community