org.llm4s.jev.JevRequest
See theJevRequest companion object
One evaluation: a state and the named questions to ask about it.
val request = JevRequest(
"Charged twice; please refund",
Map(
"route" -> JevQuestion.choice("Which team should handle this?", "billing" -> "Payments and refunds", "technical" -> "Product issues"),
"urgent" -> JevQuestion.noul("Does this need immediate human attention?")
)
)
The answers come back under the same ids as the questions, which the model never sees. All questions are answered against the one state in a single call, so ask everything you might need at once.
Value parameters
- headers
-
extra HTTP headers for this request, sent unchanged on every retry of it; one replaces a configured header of the same name, whatever its case. The client sets the credentials, content type and
Acceptheader itself and refuses to have them replaced. - model
-
the model to use, or
Nonefor the client's configured model (jev-latestby default) - questions
-
the questions, by the id their answers come back under
- state
-
what to evaluate: a string, or a JSON object or array for structured data
Attributes
- Companion
- object
- Graph
-
- Supertypes
-
trait Serializabletrait Producttrait Equalsclass Objecttrait Matchableclass Any
Members list
In this article