Jev chat reading intent

Classify a chat message by what it is trying to do

Provide a chat message and relevant thread context. Distinguish a practical answer, information request and suggestion, keeping mixed purposes for review.

chat reading intentLive API
Try an example

The viewer asks for information.

Source: API-collected workflow inspiration; original demonstration below

Source and example scope

This is an independently authored text demonstration inspired by the linked X discussion. Its rules and synthetic inputs are ours. It does not reproduce the author’s application, verify reported outcomes, or perform an external action.

Choose the message reading intent.

Decision rules and labels
HelpQuestionFeedbackOtherReview
A real response from the Jev API

Edit any input to explore a different decision. No request is sent until you run it.

Your next decision

Not run yet

Choose an example or write your own input, then run it to see the ranked choices.

Results are not stored by this site. Your submitted text is processed by the API provider.

The decision

What the decision checks

Reading intent is a preference for which messages to surface. A host looking for questions needs a different selection from a host looking for answers to a technical problem.

This taxonomy keeps practical help separate from feedback about the stream. The same sentence may serve a different role in another thread, so supply the question it answers when that context matters.

Jev Chat for Twitch filters messages by selected reading categories. This original text example uses a smaller taxonomy and does not connect to Twitch, delete messages or judge whether someone should be banned.

This is an independently authored text demonstration inspired by the linked X discussion. Its rules and synthetic inputs are ours. It does not reproduce the author’s application, verify reported outcomes, or perform an external action.

Illustration of one spreadsheet row producing two separate classification results
Illustration of the decision flow.
How it works

Try the example in four steps

Use the sample to understand the rule, then test your own input for chat reading intent.

  1. Illustration of adding the text or evidence for a decision

    Add the information to check

    Provide a chat message and relevant thread context.

  2. Illustration of defining a question and its allowed choices

    Confirm the question and labels

    Open the decision rules and keep the intended distinction between Help, Question, Feedback, Other, Review. Edit the choices only when testing your own rule.

  3. Illustration of sending one input and comparing the returned choices

    Run the decision

    Use a sample first, then try your own input. Compare the selected label with the other returned probabilities.

  4. Illustration of reviewing a result and an uncertain item before using it

    Review the next step

    Review Review before using a result. The label is a decision about the supplied information, not an executed action.

Our API test

Recorded API observations

Recorded API observations
Original inputObserved labelLeading probability
A direct viewer questionQuestion100%
Answering a shortcut questionHelp100%
Readability suggestionFeedback99.0%
A greetingOther100%
Two equal purposesReview91.0%
Unresolved replyReview92.0%

These are six original synthetic inputs, tested once per request revision. The percentage is the leading option probability, not measured accuracy. Authored expectations and any disagreements remain in the downloadable evidence. 6 of 6 results matched the authored fixture expectations.Verified

Understand the results

Chat reading intent: six recorded examples

The downloads contain six original inputs, their expected labels and one recorded API observation per input revision. Disagreements stay visible.

Using the result in your application

The single-request SDK runner uses your private TYPESAFE_API_KEY. The offline consumer reads saved observations, checks request hashes and prints a pending output. It does not call the model or change any external system.

Replay options

Inspect saved outputs or request a new decision

View the code example
Two independent commands
# Offline: inspect the downloaded saved observations. No API key is needed.
python preview_choice_workflow.py samples.json saved-api-results.json

# Optional live request: install the SDK and set TYPESAFE_API_KEY privately.
npm install @typesafe-ai/sdk@0.6.0
node run-choice-sample.mjs samples.json case-1
# The live response prints to the terminal; it does not update saved-api-results.json.
Scope of this demo

Where this decision fits

Useful scope

  • Prototyping a questions-only reading column.
  • Testing whether supplied thread context changes a short reply.
  • Separating practical answers from presentation feedback.

Outside this demonstration

  • Using a reading preference as a content safety verdict.
  • Claiming that the page connects to or moderates a live channel.
Example FAQ

Using this example

The input contract and these limits define what the result means.

Does Other mean the message is bad?

No. It only means the message has another purpose, such as greeting the host. The labels do not measure politeness or safety.

Can a message belong to two categories?

Yes. This single-choice demonstration sends equally central competing intents to Review. A different product could ask separate questions for each intent.

Does the leading probability measure accuracy?

It describes the distribution over the supplied choices for this request. These six synthetic examples are functional tests with authored expectations, not a production accuracy benchmark.

Will a result change an external system?

No. The demo displays a label and distribution. The downloadable consumer produces a pending preview packet. Application code and a separate authorization policy would control any real action.

Test a different input

Edit the example above to see how a changed fact affects the decision, or open the Playground for another task.