Jevvy — zliv83

Run cargo add [email protected] and cargo add tokio --features macros,rt-multi-thread. Set TYPESAFE_API_KEY, build a NoulQuestion and Questions, then call Jev::from_env()?.ask(&questions).await? and read the answer with reply.answer(&about_apple)?.

Jevvy reads the TYPESAFE_API_KEY environment variable through Jev::from_env(). The optional dotenvy feature adds Jev::from_dotenv(), which finds a .env file in the current or a parent directory; existing environment variables take precedence. A missing key returns JevvyError::MissingApiKey.

Jevvy supports NoulQuestion for yes/no, ChoiceQuestion with 1–255 options, and ScoreQuestion with 2–10 levels ordered lowest first. Questions::builder().state(...).question(&q).build() can combine questions about the same state in one request, and you can mix question kinds.

No. Jevvy returns values exactly as Jev sent them, without rounding or clamping. A Score can fall between levels, such as 1.6. A Noul value near 0 means a confident no, and low Choice or Score confidence means the probabilities are spread out.

Jevvy is async. The quickstart uses Tokio with the macros and rt-multi-thread features, added with cargo add tokio --features macros,rt-multi-thread. The example main function is annotated with #[tokio::main] and awaits jev.ask(&questions).

JevvyError covers HTTP failures, non-2xx responses from Jev, decoding, missing API keys, builder validation, and answer lookups such as MissingAnswer or WrongAnswerKind. A missing or unreadable .env file with the dotenvy feature returns JevvyError::Dotenv.

Avoid relying on Jevvy if you need a stable API or a derive interface today. The 0.2.0-alpha.1 builder interface has been tested with live calls, but the API is still changing, a derive interface is only planned, and the previous 0.1.0-alpha.1 release had a different API.