API · Last updated 2026-09-21

Jev API evidence fields

Evidence is material you already retrieved: passages, quotes, records. Put it in state (or structured instructions). Jev returns typed judgments about that material — not a first-class citations[] array.

This page is for builders who searched an extra “endpoint” name. jev.pro is an independent unofficial field guide — not affiliated with TypeSafe AI. We do not sell or issue keys. Confirm first-party routes on docs.typesafe.ai/api.

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

Steps

1. Retrieve and filter in code. Unused evidence still bills as input and can distract jev-1.13.
2. Name fields; point questions at backtick paths.
3. Ask whether a claim is supported (Choice/Noul) — cite pattern.
4. Persist the evidence ids you used next to the answers.

Request / response shape

No documented evidence request key. State may be a string, object, or array of text. Answers stay primitive-shaped.

Pitfalls

• Hoping Jev will fetch URLs. It evaluates text you send.
• Dumping a whole corpus into one state.

See also

• API hub
• state
• jev api cite endpoint
• jev glossary evidence bundle

FAQ

Does the API return highlighted spans?

Not as a documented field. You keep offsets if you need them.

RAG cookbook?

TypeSafe documents classifying RAG passages. Retrieval stays yours.

Is evidence an official TypeSafe type?

No. Working name on this site.

What this page does not claim

• Official TypeSafe status, logos, or support.
• That jev.pro sells, issues, or proxies API keys.
• Extra first-party HTTP routes beyond POST /v1/systemone and GET /v1/models unless the API reference lists them.
• Invented latency SLOs, search volume, or unofficial prices. List price and rate limits are vendor claims — confirm on models.
• That a schema-constrained answer is automatically factually correct.

Disclaimer

This is an independent unofficial site and is not affiliated with TypeSafe AI; official documentation is available at https://docs.typesafe.ai. Never treat jev.pro as TypeSafe official documentation. We do not sell, issue, or proxy API keys.