Jev landing promise alignment

Check whether a landing page supports an ad's promise

Give the ad's specific promise and landing-page excerpt. Compare support, contradiction and a page that leaves the promise unestablished before revising the copy.

Does the page support the ad’s specific promise?Live API
Try an example

Original input for the Promise supported 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.

Compare the exact promise with landing-page evidence.

Decision rules and labels
Promise supportedPromise contradictedPromise not establishedUnclear promiseNeed 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

A page can be silent without contradicting the ad.

Promise not established preserves a gap in the supplied excerpt. It differs from an explicit statement that a feature is unsupported. Neither label requires guessing the rest of the page.

The broad-format fixture checks a universal promise against a narrow capability statement. A specific limitation is relevant evidence even when the page also lists a working feature.

This review compares supplied text only. It does not visit a live landing page, confirm actual product behavior or establish compliance with advertising rules.

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 selecting a caption token for emphasis in an edit timeline
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 and landing-page alignment.

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

    Add the information to check

    Give the ad's specific promise and landing-page excerpt.

  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 Promise supported, Promise contradicted, Promise not established, Unclear promise, 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 Unclear promise, 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
Matching format supportPromise supported74.0%
Format conflictPromise contradicted100%
Page stays silentPromise not established94.0%
Vague promotional phraseUnclear promise73.0%
Narrow support does not cover morePromise contradicted100%
Page absentNeed 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 ad-to-page consistency
  • Separating an evidence gap from an explicit contradiction
  • Replaying the exact synthetic requests and inspecting their distributions

Outside this demonstration

  • Verifying product behavior from marketing copy
  • Inferring omitted sections of a landing page
  • Treating six fixture expectations as measured production accuracy
Example FAQ

Questions about landing promise alignment.

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

Does Promise supported verify the product feature?

No. It means the supplied page text supports the promise. Product behavior needs independent testing.

Why not treat page silence as contradiction?

Silence leaves the promise unestablished in this excerpt. Contradiction requires explicit conflicting evidence; preserving that distinction helps a reviewer request the right information.

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 landing promise alignment input

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