Question 1

Is this the official TypeSafe Rails gem?

Accepted Answer

No. It is built on the community typesafe-sdk Ruby gem and states plainly that it is not an official TypeSafe package. The SDK stays framework-neutral; this gem adds Rails configuration, persisted usage and cost telemetry in a typesafe_calls table, and an opt-in persistence-backed confidence policy for Choice and Score.

Question 2

What happens if I call act! without creating a policy first?

Accepted Answer

It raises Typesafe::Rails::MissingPolicyError, which is the fail-closed point. With a DecisionPolicy row in place, a below-threshold answer runs your fallback, given either as one lambda or as a hash of handlers per mode; fallback: escalate raises LowConfidenceError instead. Intentionally ungated reads should use result[:key] directly.

Question 3

Will it log my ticket bodies somewhere?

Accepted Answer

SDK logging is opt-in and stays off unless you assign config.typesafe.logger. At debug level the Ruby SDK logs request and response bodies, so enabling it may place application state in logs. Telemetry rows carry decision type, returned model, token counts, rates, estimated cost, request ID and latency, not the payload itself.

Question 4

Will the recorded cost numbers be real or invented?

Accepted Answer

They are estimates from published rates, and unknown model families record cost_usd = NULL rather than an invented price. A built-in Jev family rate lets jev-latest resolve to versioned names such as jev-1.13.0 without losing the estimate; override pricing when TypeSafe changes its rates. A telemetry database failure is non-fatal unless strict_logging is true.

Question 5

How do I add it to an existing Rails app?

Accepted Answer

bundle add typesafe-ai-rails, run bin/rails generate typesafe:rails:install, then bin/rails db:migrate. Add the key under typesafe: api_key in Rails credentials. The gem loads through typesafe-ai-rails, while the stable Ruby API stays under Typesafe::Rails and direct users may also require typesafe/rails.

Question 6

Why bundle every question into one ask call?

Accepted Answer

Because ask sends all questions about the same state in one System One request, which follows TypeSafe's recommendation to batch independent questions that share state. A single call can mix Choice, Noul and Score keys, and the returned Result exposes them separately as result[:key], choices, scores and nouls.

Question 7

Does a Noul answer carry its own confidence value?

Accepted Answer

No. The README is specific: Noul has no separate confidence, its noul field is the probability of yes. Choice and Score are the answers that carry confidence, which is why act! gates those two while Noul is thresholded directly, for example escalate when urgent.noul >= 0.8.

TypeSafe AI Rails

About this project

Highlights

Quickstart

Questions about this entry

From the Jev guides

From the Jev AI model community