Open · Last updated 2026-09-21

Questions for Jev buyers

Buyers should interrogate TypeSafe and any gateway, not jev.pro. We do not sell Jev. These questions keep you from buying a chatbot by accident.

Independent procurement checklist — not TypeSafe sales, not a reseller, not a key shop. Confirm current commercial facts on docs.typesafe.ai. Replicas and third-party “Jev” SKUs you meet in the wild are not Jev and not endorsed.

Ask the vendor

1. What versioned ids can we pin, and how do aliases move?
2. What is the current list price and what is not included (support, higher RPM)?
3. DPA, subprocessors, ZDR — written where?
4. Is customer data used for training? (They say no — get the current Legal.)
5. Fine-tune / LoRA availability? (Public docs: no.)
6. Documented error set vs marketplace extra codes (402, verification).
7. Language support beyond English?
8. Roadmap for jaggedness items?

Ask yourselves

Can we fail closed? Who owns criteria? What is the irreversible action? Do we have gold labels?

Red flags in a pitch

• “Jev replaces your rules engine, KYC vendor, and LLM.”
• Unpublished latency SLOs presented as ours.
• Keys sold by a guide site.
• Fine-tune promises that contradict public “no customer LoRA.”
• A URL tree that is a photocopy of a rival handbook.

Procurement questions that survive a legal review

Ask TypeSafe and any gateway, in writing. jev.pro cannot countersign.

Access and pin

• Which versioned ids can we pin? How do jev-latest and jev-preview move?
• What string does this door expect (jev-1.13.0 vs typesafe/jev-1.13)?
• Where do keys come from? (Their console or a marketplace. Never this site.)

Money and limits

• Current list price? Models page has listed $0.042 / M input with output free — vendor claim; confirm.
• What is not included (support, higher RPM, ZDR SKU)?
• Are rate limits contractual or dynamic? TypeSafe has said limits can be dynamic — plan 429s.

Paper

• DPA, subprocessors, breach clock — current Legal, not a blog.
• Training representations (they have said no on customer requests/responses — get the clause).
• Fine-tune / LoRA? Public docs we used: no customer LoRA. Treat a pitch that contradicts that as a red flag.

Fit

• Language support beyond English?
• Documented error set vs marketplace extras (402, verification)?
• Roadmap for jaggedness items (math, dates, generation)?
• High-risk use restrictions?

Then ask yourselves: can we fail closed? Who owns criteria? What is the irreversible action? Do we have gold labels? Cost math belongs on cost planning; counsel questions on questions for legal; enterprise posture on for enterprises.

Red flags that are not “negotiation”

• “Jev replaces your rules engine, KYC vendor, and LLM.”
• Unpublished latency SLOs presented as your measurement.
• Keys sold by a guide site.
• Fine-tune promises that contradict public “no customer LoRA.”
• A URL tree that is a photocopy of a rival handbook.
• A vendor who will not distinguish SemIf/OpenJev from hosted Jev.

Schema-safe ≠ factual correctness. Do not buy a “cannot hallucinate” warranty that means “stays in the JSON schema.”

When not to use this page’s advice

Do not send this list as if jev.pro were in the deal. Do not treat our unofficial stance as a TypeSafe disclosure. Do not buy keys from us — we have none. Do not score an open replica as a Jev substitute in the RFP.

What this page does not claim

• Not a sales brochure.

FAQ

Can we buy keys from jev.pro? No.

Is this official RFP language? No. Counsel edits.

Is $0.042 / M a contracted rate? It is a vendor list price we read on the models page. Confirm, and ask what is excluded.

Should we evaluate OpenJev in the same RFP tab? Only as a separate, non-Jev line. It is not Jev and not endorsed.

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.

Open-cluster pages are independent field-guide notes. Replicas and third-party interfaces mentioned anywhere on jev.pro are not Jev and not endorsed. Hub: Open. Siblings: for enterprises, questions for legal, cost planning. Canonical: https://docs.typesafe.ai.