API· Last updated

Jev API Evidence Fields

The public API reference documents one evaluation route — POST https://api.typesafe.ai/v1/systemone — plus GET /v1/models. This page title is not a separate first-party URL in that reference. Treat the capability as something you implement around the official call.

Put passages, records, and quotes in state (or structured instructions). Answers are typed judgments about that material, not a citation list. This site does not sell, issue, or proxy TypeSafe keys. Authenticate with a credential you already have from the console or a documented gateway.

Related search language: Jev API evidence fields, TypeSafe Jev, Jev decision model, decision automation.

See also the api hub.

Jev API Evidence Fields: context

Cookbooks that “check citations” still require you to supply the source span. Jev does not fetch URLs.

Jev API Evidence Fields: inputs

Name evidence fields. Point questions at them with backticks. Filter unused passages (jaggedness + cost).

Jev API Evidence Fields: decision logic

If you need to show “why,” display the state spans you sent plus probabilities — not a generated rationale.

Jev API Evidence Fields: implementation notes

State docs: concepts/state. We will not invent answers.evidence.

FAQ

Is this a documented TypeSafe URL?

No. The public reference lists POST /v1/systemone and GET /v1/models. This title is an application pattern around that contract — not a cloned rival endpoint list.

How should I implement it?

Keep one evaluation POST. Put batching, jobs, search, or policy in your code. Do not invent /v1/batch or similar unless TypeSafe documents it.

Does jev.pro issue keys or OpenAPI?

No. Use official SDKs and docs.typesafe.ai. We do not sell credentials.

What this page does not claim

Disclaimer

This is an independent unofficial site and is not affiliated with TypeSafe AI; official documentation is available at https://docs.typesafe.ai.

Primary documentation: https://docs.typesafe.ai. Never treat jev.pro as TypeSafe official documentation. We do not sell, issue, or proxy API keys.

Sources

Public TypeSafe or adjacent documentation only. No private claims.