Jev rental claim checklist

Choose how to verify a rental-listing claim

Read one fictional listing claim to choose a viewing check, a document request or a review of vague promotion. The result suggests an evidence channel rather than deciding legality or liability.

rental claim checklistLive API
Try an example

This is a property feature to inspect.

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.

For one rental listing claim, choose a verification approach.

Decision rules and labels
Viewing checkDocument requestVague promotionReview
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 example makes a checklist suggestion for one claim. It does not verify the property, establish legal rights or recommend a tenant or landlord.

Some claims need more than one kind of evidence. Separate them into clear statements or keep the combined item in Review.

The linked rental prototype turns listing statements into checks. Our fictional text samples cover the evidence-channel part and do not reproduce its full assessment.

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 choosing one tool from the supplied alternatives
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 rental claim verification.

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

    Add the information to check

    Read one fictional listing claim to choose a viewing check, a document request or a review of vague promotion.

  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 Viewing check, Document request, Vague promotion, 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
Physical conditionViewing check100%
Renovation historyDocument request99.0%
Subjective praiseVague promotion100%
Contract termDocument request98.0%
Two claim channelsReview95.0%
Unspecified claimVague promotion94.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 Unspecified claim, the expectation was Review; the observed choice was Vague promotion.Verified

Understand the results

Rental claim verification: 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

  • Preparing questions before a property viewing.
  • Separating observable features from claims that need records.
  • Identifying listing statements that need to be split into separately checkable claims.

Outside this demonstration

  • Assessing housing eligibility or the trustworthiness of a real person.
  • Treating a checklist label as proof that a property is safe or compliant.
Example FAQ

Using this example

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

Does Document request mean the claim is false?

No. It means the claim concerns information that cannot be established by the supplied listing sentence alone.

Can Viewing check establish a guarantee?

No. A viewing provides limited observations. Qualified inspections, records and local requirements may still matter; this demo does not evaluate them.

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.