API · Last updated 2026-09-21

Jev API cite endpoint

The official citation-check cookbook uses a Choice (or similar) on whether context supports a claim, plus confidence to hold a citation. There is no documented /v1/cite.

This page is for builders who searched an extra “endpoint” name while wiring Jev / System One. 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. You already have a claim and candidate passages in state.
2. Ask whether the passage supports the claim.
3. If confidence is low, do not emit the citation.
4. Keep offsets and URLs in your store — Jev will not invent a bibliography.

Map onto the official POST

Same evaluation POST. Put claim + passage in named fields. Point instructions at backtick paths. Choice (max 255) among support labels, or Noul “does this passage support the claim?” Noul has no confidence — threshold the probability. Choice/Score expose confidence. Question ids are not sent to the model.

Jev evaluates text you send. It does not browse the web. Asking it to generate a citation string is the wrong product shape. Schema-safe “supported” ≠ the passage is true in the world. Pin jev-1.13.0; jev-latest / jev-preview currently resolve there — confirm.

Documented errors: 401, 422, 429, 529. Official SDKs retry 429/529. Vendor-claimed context (64k / 32k) is why you send the passage, not the corpus. TypeSafe documents the double-checking citations path — read it at the source.

When not to use this pattern

If you do not yet have a claim and a passage, retrieve first (search pattern). If you need a generated MLA string, call an LLM after and label it.

Pitfalls

• Asking Jev to generate a citation string. Generation is the wrong product shape.
• Schema-safe “supported” ≠ the passage is true in the world.
• Calling /v1/cite.
• Emitting a cite when Choice confidence is low.

See also

• API hub — evaluation POST
• Evidence fields — what you persist
• Extract pattern — pick spans, then cite
• Jaggedness — do not over-trust numeric polish

FAQ

Is this a documented TypeSafe URL?

No. Cookbook + evaluation POST.

Can Jev browse the web?

It evaluates text you send.

Double-checking citations cookbook?

Yes — TypeSafe documents that path. Read it at the source.

Where do URLs live?

In your store. Not in a generated bibliography field.

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.