Jev credentialed CORS boundary

Review which origins a credentialed CORS policy trusts

Give the endpoint purpose, origin matcher and credentials setting. Compare an exact allowlist with broad reflected origins and missing policy details.

credentialed CORS boundaryLive API
Try an example

The complete policy names the allowed origin precisely.

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 CORS response policy.

Decision rules and labels
Exact policyBroad trustPublic noncredentialedReview
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

CORS concerns which browser origins may read a cross-origin response. With credentialed responses, unrestricted origin reflection is different from an exact allowlist of intended application origins.

A literal wildcard combined with credentials is also different from reflecting an arbitrary concrete origin. Browsers reject the wildcard combination for credentialed reads; the example treats it as a configuration needing review, not proof of successful access.

The linked linter checks credentialed-origin trust. This exercise does not send cross-origin requests. Authentication, CSRF protection, cookie attributes and server permissions remain separate 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 reviewing messages against supplied policy categories
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 credentialed cors.

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

    Add the information to check

    Give the endpoint purpose, origin matcher and credentials setting.

  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 Exact policy, Broad trust, Public noncredentialed, 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
Exact allowlistExact policy96.0%
Reflect any originBroad trust77.0%
Weak substring matcherBroad trust80.0%
Public data endpointPublic noncredentialed99.0%
Unknown origin callbackReview88.0%
Literal wildcard with credentialsReview81.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

Credentialed CORS: 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 an origin callback used with credentials.
  • Distinguishing exact-origin matching from a weak substring check.
  • Separating a public data endpoint from user-specific responses.

Outside this demonstration

  • Probing a real site or claiming cross-origin data access occurred.
  • Treating CORS configuration as proof of complete authentication or CSRF protection.
Example FAQ

Using this example

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

Does a wildcard expose every credentialed response?

Not as a literal Access-Control-Allow-Origin: * response. Browsers reject that combination for credentialed reads. Reflecting arbitrary concrete origins is a different configuration.

What makes two origins the same?

The scheme, hostname and port matter. This example supplies an explicit parsed exact-origin policy rather than relying on a substring of a URL.

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.