Sapling RCM switches search router from chat model to Jev, cutting latency and cost

Sapling RCM, a medical billing app, added record search where users press ⌘K and query across eight tables, and a small model routes each query to the relevant tables. The team compared Jev, a non-chat probability model from TypeSafe served via OpenRouter, against Gemini 3.5 Flash-Lite. Jev's median routing call took 466 ms versus 900 ms for Gemini, and it cost about $23 per million searches compared with $170. Jev missed results on 3 of 27 searches, while Gemini missed on 6 of 30. The approach asks the model what kind of text was entered, such as a person's name or claim number, and maps those types to tables in application code.
This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)
Log in to join the discussion and vote.
Log in