JEV
JEV (preview)
jev-previewProvider
JEV
Input $/1M
$0.427
Output $/1M
Gratis
Tentang
JEV is a typed-decision API, not a chat model. You send a request shaped as {model, state, questions} — where state is the context to decide over and questions is the set of typed questions to answer — and get back structured JSON with a calibrated probability, category, or score per question, instead of free-form text you'd need to parse. It's built for pipelines that need a decision, not a conversation: ticket classification, routing, and scoring workflows where downstream code consumes the response directly.
Tipe pertanyaan
Apa yang dijawab model ini
noulA yes/no binary question, answered with a calibrated probability rather than a flat label
choicePicks one category out of a set of N you define (e.g. billing vs technical vs sales)
scoreA numeric score on a scale you define (e.g. 1-5 frustration score)
Kemampuan
Apa yang bisa dilakukan API ini
- ●Answers noul (yes/no), choice (category), and score (numeric) questions in one call
- ●Returns a calibrated probability alongside binary answers, rather than just a label
- ●Accepts multiple questions per request against the same state
- ●Structured JSON output — no prompt engineering needed to parse the answer
Cocok untuk
Kasus penggunaan umum
- ✓Customer-support ticket classification (routing by category)
- ✓Routing decisions — e.g. billing vs technical vs general inquiry
- ✓Sentiment or frustration scoring on incoming messages
- ✓Any workflow that needs a structured decision instead of free-form chat text
Batasan
Ketahui sebelum mengintegrasikan
- !Typed-decision only — this is not a chat/completion model, and does not accept free-form conversational prompts
- !US-hosted: the state you send egresses to the US for processing (mitigated by Anoman's PII masking applied to state before it leaves the region)
- !Billed on input only — output tokens are free, so cost scales with the size of the state + questions you send, not the length of the answer
- !Early-access channel — behavior may change between releases more than the pinned or latest channels
Bagaimana ini diukur
Kalibrasi, bukan skor leaderboard
Setiap jawaban membawa nilai probabilitas atau confidence yang terkalibrasi bersama label, pilihan, atau skornya — model ini dirancang untuk menyatakan seberapa yakin dirinya, bukan hanya apa yang dipilih. Anoman tidak mempublikasikan, dan tidak mengarang, angka akurasi atau performa untuk model ini.
Bandingkan antar model JEV
Kanal rilis, bukan tingkat performa
jev-latest, jev-preview, dan rilis tetap seperti jev-1.13.0 adalah API keputusan bertipe yang sama di bawah kanal rilis berbeda — bukan produk terpisah dengan kemampuan berbeda.
| Model ID | Kanal rilis | Input $/1M |
|---|---|---|
| jev-1.13.0 | Pinned/stable release — deterministic behavior across upgrades of jev-latest / jev-preview | $0.427 |
| jev-latest | Rolling alias — always tracks JEV's latest release; currently resolves to jev-1.13.0 | $0.427 |
| jev-preview | Early-access preview channel — currently resolves to jev-1.13.0 | $0.427 |
Contoh kode
Panggil jev-preview
curl https://api.anoman.io/anoman/v1/decisions \
-H "Authorization: Bearer anm-sk-..." \
-H "Content-Type: application/json" \
-d '{
"model": "jev-preview",
"state": "Customer: My invoice charged me twice this month and I need this fixed today.",
"questions": {
"is_urgent": {
"type": "noul",
"instructions": "Is this ticket urgent and time-sensitive?"
}
}
}'