Jev ad offer mechanism

Identify the offer stated in an ad

Paste an ad excerpt to identify trial access, a price discount or a bundle. Keep feature descriptions separate from an actual offer and its stated terms.

What offer is explicitly stated?Live API
Try an example

Original input for the Trial access outcome. Edit the evidence to send a new request.

Source: Background discussion on X

Source and example scope

These fictional inputs and decision rules were written for this page. The linked X discussion provides background; the technical implementation follows TypeSafe's Choice contract.

Classify the stated offer mechanism.

Decision rules and labels
Trial accessPrice discountBundleNo explicit offerNeed evidence
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

Saving time is not a stated price discount.

An offer mechanism describes what the copy explicitly proposes. A feature benefit such as saving time does not establish a reduced price, a trial or a bundle.

The labels do not verify that terms are honored or calculate savings. Exact prices, eligibility and deadlines must come from verified commercial data and ordinary validation.

The source describes tagging ad offers. These fictional excerpts isolate that task without adopting its claimed dataset size or performance measurements.

These fictional inputs and decision rules were written for this page. The linked X discussion provides background; the technical implementation follows TypeSafe's Choice contract.

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 ad offer type.

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

    Add the information to check

    Paste an ad excerpt to identify trial access, a price discount or a bundle.

  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 Trial access, Price discount, Bundle, No explicit offer, Need evidence. 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 Need evidence 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
Trial periodTrial access100%
Price reducedPrice discount100%
Items packagedBundle99.0%
Feature onlyNo explicit offer93.0%
Saving time is not priceNo explicit offer100%
No copy excerptNeed evidence100%

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

Source and example scope

Compare each saved result with its authored expectation. A disagreement remains in the fixture review; the call is not repeated to obtain a preferred label.

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.

Runnable offline example

Run one sample, then inspect the local packet

View the code example
Single-request replay
npm install @typesafe-ai/sdk@0.6.0
# Set TYPESAFE_API_KEY privately in your shell.
node run-choice-sample.mjs samples.json case-1
python preview_choice_workflow.py samples.json saved-api-results.json
Scope of this demo

Where this decision fits

Useful scope

  • Reviewing explicit mechanisms in creative copy
  • Separating feature benefits from commercial offers
  • Replaying the exact synthetic requests and inspecting their distributions

Outside this demonstration

  • Calculating a discount from incomplete prices
  • Guaranteeing eligibility or promotional terms
  • Treating six fixture expectations as measured production accuracy
Example FAQ

Questions about ad offer mechanism.

The rubric explains the decision; the application owns the next step.

Does Trial access mean free?

No. The excerpt may describe trial access without stating a price. The classifier must not invent a free offer or its conditions.

Can one ad have a bundle and a discount?

Yes. This simple taxonomy assumes one primary mechanism. For equally central mechanisms, extend the contract with mixed or multiple outcomes and test that revision.

Does the leading probability measure production accuracy?

No. It is the model distribution for this one request. The six examples are functional checks with authored expectations, not a representative benchmark. Inspect disagreements and evaluate your own examples before using the label.

What happens when the API fails?

The window shows an error and supplies no fresh judgment. The downloadable runner sends one request without retries. Need evidence is a valid outcome about incomplete input; it does not stand in for a network or provider failure.

Try your own ad offer mechanism input

Edit the evidence above or use the Playground to test another bounded question.