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 checklist. docs.typesafe.ai.
Ask the vendor
- What versioned ids can we pin, and how do aliases move?
- What is the current list price and what is not included (support, higher RPM)?
- DPA, subprocessors, ZDR — written where?
- Is customer data used for training? (They say no — get the current Legal.)
- Fine-tune / LoRA availability? (Public docs: no.)
- Documented error set vs marketplace extra codes (402, verification).
- Language support beyond English?
- 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.
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.
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.
Sources
Public TypeSafe or adjacent documentation only. No private claims.