Support ticket classification with a review path
Turn an incoming customer message into one of the queues your team already uses. Keep the category list small, the routing rule explicit, and the final action under your control.
Read the guide ↗STRUCTURED DECISIONS. CLEAR NEXT STEPS.
Jev API. Turn messy messages into clear next steps.
A Jev API workspace for support, sales, and operations. Define your labels, test a real message, and route uncertain results to a person.
3 anonymous attempts per day · 20 signup credits · No card for the trial
JEV
API
API
One label.
Confidence you can inspect.
A review path when it matters.
JEV / DECISION LABYOUR RULES. YOUR LABELS.
OUTPUT / JSON
Your decision
Illustrative sample — not a live model response.
Run a decision or open the labeled sample to see the result here.
A high score is not a guarantee. Keep a person in control of consequential actions.
API docs →Use cases
Use cases →Start where the work piles up.
AI lead qualification using your sales criteria
A good qualification rule explains why a lead belongs in a queue. Evaluate the information a prospect actually provided against a short, written definition of fit.
Read the guide ↗An intent classification API with explicit outcomes
Route a message to the next step without asking a chat model to write a paragraph. Supply the message, your allowed intents, and the rule that separates them.
Read the guide ↗01 / Define your rule
Choose the outcomes your team actually uses.
02 / Inspect the decision
See the label, confidence when available, and review flag.
03 / Connect your workflow
Use the API when the result is ready for your process.
API docs
A decision fits your stack when its boundaries are clear.
Explicit labels, visible failures, and idempotency keys. Your application stays in control of every action.
API docs ↗POST /api/v1/decisions
curl https://jevapi.pro/api/v1/decisions \
-H 'Authorization: Bearer YOUR_API_KEY' \
-H 'Content-Type: application/json' \
-H 'Idempotency-Key: ticket-123-v1' \
-d '{
"text": "I was charged twice this month.",
"instructions": "Choose the responsible team.",
"labels": ["billing", "technical", "account"],
"threshold": 0.85
}'Integration example. Replace YOUR_API_KEY with a key stored on your server.
Questions before your first decision
Is this the official Jev website?
No. Jev API Pro is an independent workspace. Jev is a model from TypeSafe, accessed here through OpenRouter.
Can I try it without an account?
Yes, when live decisions are available: up to three attempts per source address per UTC day, subject to shared trial capacity. A labeled example is also available.
What happens when the model fails?
We show an explicit error. Failed account decisions are refunded, and we do not substitute a different model silently.
Do you store the messages I submit?
Decision history stores the result, request hash, and operational metadata, not the submitted message. Your text is sent to OpenRouter and its model provider for inference.
What does a credit buy?
One completed classification within the published input limits uses one credit. Signed-in accounts receive 20 signup credits and can claim two daily check-in credits.
Can I automate business actions?
Use the API to get decisions. Your own application checks permissions and performs actions. Low-confidence or missing-confidence results should go to review.