Jev recurring charge cues

Look for recurring-payment cues in a transaction description

Read one fictional billing description for explicit renewal, subscription or installment language. Distinguish a stated one-off purchase from absent or conflicting recurrence evidence without predicting future charges.

recurring charge cuesLive API
Try an example

Periodic renewal is stated directly.

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.

Read the supplied billing description.

Decision rules and labels
Recurring cueOne-off cueNo recurrence evidenceReview
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

This label records what the description says. Recurring cue does not prove that another charge will occur; a subscription may later be cancelled or its terms changed.

One-off cue requires an explicit one-time statement. When the text simply names a store or shows a card purchase, No recurrence evidence preserves that gap.

The linked transaction recipe includes a recurrence question. Our synthetic examples isolate the wording check and do not access a bank account, compute payment dates or categorize spending.

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 recurring payment cues.

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

    Add the information to check

    Read one fictional billing description for explicit renewal, subscription or installment language.

  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 Recurring cue, One-off cue, No recurrence evidence, 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
Monthly renewalRecurring cue100%
Installment seriesRecurring cue100%
Single licenseOne-off cue100%
Merchant onlyNo recurrence evidence91.0%
Conflicting termsReview98.0%
No detailNo recurrence evidence51.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. 5 of 6 results matched the authored fixture expectations. For No detail, the expectation was Review; the observed choice was No recurrence evidence.Verified

Understand the results

Recurring payment cues: 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

  • Testing subscription-cue labeling with fictional bank descriptions.
  • Distinguishing one-time license wording from renewal wording.
  • Keeping uncertain charges out of an automatically inferred subscription list.

Outside this demonstration

  • Predicting account activity or giving a complete subscription inventory.
  • Cancelling payments, computing repayment schedules or making financial recommendations.
Example FAQ

Using this example

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

Does No recurrence evidence mean it will not happen again?

No. It means the provided wording does not establish recurrence. Another transaction record or the actual billing terms may add information.

Why count an installment as a recurring cue?

This taxonomy includes an explicitly stated payment series. If your product separates installments from subscriptions, define separate choices and retest both.

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.