Laya · DECISION MODEL

Laya English

The English-optimized Laya model for structured decision requests.

convaiinnovations/layachoicescorenoul

Try this model Back to models

MODEL PROFILE

Laya

MODEL ID

convaiinnovations/laya

STRUCTURED OUTPUT

choice

score

noul

Use the Laya endpoint when you want the Laya-specific contract and language routing.

Interactive playground

Try typed decisions on your own text

Pick an example or add your context. Ask choice, score or yes/no questions, then inspect the structured answers and probabilities.

Requests consume account credits. See the returned result for the actual credits used.

Read the Laya API integration guide

Workbench

Example library

What do you want to decide?

Choose a scenario to load editable input and rules. Loading an example uses no credits.

Examples load into the current draft only; no configurations or run history are saved.

ModelInput format

State

Provide the context shared by every question.

Text

Input state

All questions share this context and are answered independently.

Questions

Define up to eight typed questions for the same state.

3 / 8

3. Run decision

Run the decision request.

Result preview

Subject: Charged twice again!! Hi — this is the SECOND month in a row I've been billed twice for the Pro plan. I already emailed last month and nobody replied. I run my whole business on this. If it's not refunded today I'm cancelling and disputing the charge with my bank.

↓One input → multiple structured decisions

Click “Generate decisions” to see typed output with probabilities.

Results are returned in a structured format so you can connect them to your application logic.

WHERE IT FITS

A model page for a clear decision boundary.

Use the Laya endpoint when you want the Laya-specific contract and language routing.

English workflows

Define the question, receive a typed signal, and connect the result to the next step in your workflow.

Support triage

Define the question, receive a typed signal, and connect the result to the next step in your workflow.

Agent routing

Define the question, receive a typed signal, and connect the result to the next step in your workflow.

ONE CONTRACT

Use the same decision shape in production.

The model changes, but your integration can keep a state, typed questions, and a predictable response contract.

Read the API docs

REQUEST EXAMPLE

POST /laya/v1/systemone

{
  "model": "convaiinnovations/laya",
  "state": "A customer reports a duplicate charge and needs a fast resolution.",
  "questions": {
    "route": {
      "type": "choice",
      "criteria": {
        "billing": "send to billing support",
        "account": "send to account support",
        "urgent": "escalate for immediate review"
      }
    },
    "urgent": {
      "type": "noul",
      "instructions": "Does this request need attention now?"
    }
  }
}