Jev 1.13 - MixRoute API

TypeSafe Jev 1.13 provides typed Choice, Score and Noul decisions. The pinned ID jev-1.13.0 and stable alias jev-latest currently point to the same model, with the same parameters, capabilities and pricing. Call the synchronous native endpoint; this is not generated chat text or an asynchronous video task.

Model Specifications

Item	Details
ID	`jev-1.13.0` / `jev-latest`
Version Policy	jev-1.13.0 pins the version; jev-latest currently points to it but may change in the future. Response model identifies the version used.
Input	Text strings, JSON objects or arrays; no image, audio or video input.
Output	Choice / Score / Noul
Context	64k tokens per request; 32k for state + longest question.
Input Price	$0.042 / 1M tokens
Output Price	$0 / 1M tokens

These are base USD rates; marketplace pricing, group multipliers and your bill determine final charges. Choice/Score return confidence; Noul returns a 0-1 probability directly. None guarantees a correct judgment on every call.

Request Example

Set MIXROUTE_API_KEY, then submit native JSON. Replace model with jev-latest to call the same current model through its alias.

curl --request POST "https://api.mixroute.ai/typesafe/v1/systemone" \
  --header "Authorization: Bearer $MIXROUTE_API_KEY" \
  --header "Content-Type: application/json" \
  --data '{
  "model": "jev-1.13.0",
  "state": "I was charged twice for order 123. Please refund the duplicate charge today.",
  "questions": {
    "department": {
      "type": "choice",
      "instructions": "Which team should handle this request?",
      "criteria": {
        "billing": "Duplicate charges, payments and refunds",
        "technical": "Broken software and integration issues",
        "shipping": "Shipment delivery and tracking"
      }
    },
    "urgency": {
      "type": "score",
      "instructions": "How time-sensitive is the request?",
      "criteria": [
        "No deadline; routine request",
        "Needs attention within a week",
        "Explicitly requires action today"
      ]
    },
    "duplicate_charge": {
      "type": "noul",
      "instructions": "The customer was charged twice for the same order.",
      "criteria": {
        "true": "Explicit duplicate payment for the same order",
        "false": "No duplicate payment is mentioned"
      }
    }
  }
}'

The synchronous response contains model, answers and usage. Full parameter definitions, probability semantics, code examples and billing details are in Jev Decisions API.