/v1/systemone protocol

The /v1/systemone protocol is the wire format used by TypeSafe's Jev decision API and implemented by Laya's laya-serve server and by Laya Studio. The name comes from "System 1": fast, single-pass decisions rather than long generated reasoning.

Request

POST /v1/systemone with a JSON body:

• state: a string, a JSON object, or a list of conversation turns.
• questions: an object mapping your question id to a definition with type (choice, score or noul), instructions, and criteria.
  • choice criteria: a dict of label to description, or a list of labels.
  • score criteria: a list of level descriptions, level 0 first.
  • noul criteria: optional {"true": ..., "false": ...} descriptions.
• model (optional): on Laya servers, english, multilingual or typed-decisions pins a checkpoint. Any other value, such as a Jev model id, is ignored and the request is routed automatically.

On Laya Studio, send it to https://api.laya.studio/v1/systemone with Authorization: Bearer lsk_live_....

Response

• model
• answers: one entry per question id. A choice answer has choice and probabilities; a score answer has the expected level score, a legend and probabilities; a noul answer has noul, the probability of true. Every answer has confidence and action.act_probability.
• usage: input_tokens and output_tokens (always 0 for Laya, since nothing is generated).
• routing (Laya only): which checkpoint answered and why. Jev clients ignore it.

A malformed question returns HTTP 422 with a message naming the question and the problem.

Because the shapes match, a Jev client can switch by changing its base URL and key. On Laya Studio each question in a call is billed the input tokens it reads, 15% below Jev's list price. See the /v1/systemone docs, choice, score and noul and Laya vs Jev.