API· Last updated

Jev request format

Top-level body:

Field Required Role
state Yes String, object, or array of text
model Yes jev-latest or a versioned / preview alias
questions Yes Map of your IDs → question objects

Omitting a required field is a 422 class error.

Question object

Shared: type (choice | score | noul), instructions (string, object, or array).

The map key is echoed on the answer. It is not used in inference.

Worked official example

{
  "state": "Help! My payouts have been failing for 3 days.",
  "model": "jev-latest",
  "questions": {
    "is_urgent": {
      "type": "noul",
      "instructions": "Does this convey urgency?"
    }
  }
}

For department routing and frustration scoring, copy the quick-start multi-question body rather than inventing a schema.

Sources

Public TypeSafe or adjacent documentation only. No private claims.