Jev JWT verification boundary

Check JWT signature verification before protected use

Describe the helper contract and how claims are used. Compare verified server use with decode-only authorization and nonauthoritative display, without handling a real token.

JWT verification boundaryLive API
Try an example

The signature check precedes the protected use.

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.

Review JWT claims use.

Decision rules and labels
Verified firstDecode-only trustDisplay-onlyReview
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

Decoding a JWT makes its claims readable. Signature verification addresses whether the signed content passes the verifier's cryptographic check. Those are different operations and can occur at different points in the code.

This exercise follows the claims into protected server behavior. A browser display label is deliberately separated from a server using an unverified role or tenant to grant access.

The source linter checks decode-without-verify paths. The label here covers that narrow boundary; issuer, audience, expiry, algorithm restrictions and application permissions still need their own verified controls.

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 checking a code change and reviewing a flagged line
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 jwt verification order.

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

    Add the information to check

    Describe the helper contract and how claims are used.

  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 Verified first, Decode-only trust, Display-only, 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
Verified server roleVerified first98.0%
Decoded role acceptedDecode-only trust91.0%
UI label onlyDisplay-only98.0%
Unknown auth helperReview87.0%
Verification after useDecode-only trust81.0%
Verifier result ignoredDecode-only trust84.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

JWT verification order: 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

  • Reviewing a role check built on decoded JWT claims.
  • Checking that a failed signature check stops protected use.
  • Separating display-only decoding from server authorization.

Outside this demonstration

  • Creating or testing forged tokens against a real service.
  • Treating signature verification as proof of complete authentication and authorization correctness.
Example FAQ

Using this example

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

Is decoding itself always unsafe?

No. Its use matters. This page distinguishes nonauthoritative display from trusting decoded claims for a protected action.

Does Verified first mean authentication is complete?

No. It only describes the supplied signature-check boundary. Other token and authorization checks remain outside this label.

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.