Skip to content

AI decision API · Swiss-hosted · Jev-compatible

Confidence over chat, where it matters

Laya Studio reads an email, a patient message or a review and answers your questions about it with a calibrated probability, not prose. In about a tenth of a second, processed in Switzerland.

POST/v1/systemonerequest
{"state": "pixel swallow, 6x5 grid,           wing raised, red beak", "questions": {  "is_laya_logo": {"type": "noul"},  "tone": {"type": "choice",    "criteria": ["light", "dark"]}}}
200 OK104 ms · 58 tokens
{"answers": {  "is_laya_logo": {"noul": 0.99},p 0.99  "tone": {"choice": "light"}confidence 0.86}, "usage": {"input_tokens": 58}}
Illustrative example, values written by hand. Laya reads the text; the figure only pictures what it is about.
  • ~120 ms

    per warm request, from Europe

  • 100+

    languages, routed automatically

  • $0.0357

    per 1M input tokens, 15% below Jev

  • Apache-2.0

    open model weights

How it works

Text in. Calibrated answers out.

Send a message, a ticket or any JSON with the questions you care about. Laya reads it once and returns a probability for every answer: no generated text, nothing to parse.

  • Typed questions. choice, score or yes/no, defined by you in plain words.
  • One forward pass. about a tenth of a second, no tokens generated.
  • Answers you can act on. a probability per answer, so a threshold decides, not a prompt.

See it decide

Ask a message anything. See how sure the answer is.

Five everyday messages: a refund email, a patient portal message, a product review, an incident ticket and a sales lead. See the questions Laya asks and the real answers it returned, each with how sure it is. Sign up to ask your own; every workspace starts with 6k free tokens.

Support inbox08:42
From
Dana Keller <dana.keller@example.com>
To
support@your-company
Subject
Charged twice for order #4821

Hi, I was charged twice for order #4821 ($129.00). Please refund the duplicate charge before Friday, our books close then. This is the second billing mistake this quarter and we're starting to look at other vendors.

Laya’s verdict

Refund
Real result, captured from the live API354 ms when captured

reading…

Waiting for every answer…

  1. 01What does the customer want?Pick one

    reading

  2. 02Does the message need a reply today because of a deadline or time pressure?Yes / no

    waiting

  3. 03Does the customer suggest they may leave or switch to a competitor?Yes / no

    waiting

Calibrated

Probabilities you can set policy on

Laya is trained for calibration: across many answers, the ones it scores 0.8 come true about 80% of the time. So you automate above a threshold you choose and send the rest to a person.

  • Thresholds, not prompts. pick the confidence that matches the cost of a mistake, per question.
  • Check it on your data. a few hundred labelled examples show how well the probabilities hold for you.

Three question types

Ask the questions your workflow already asks

Most decisions fit one of three shapes. Define them in plain words in the request; Laya returns a probability for every option.

choice

Pick one label: intent, category, the team to route to.

What does the customer want?

refund0.82
cancel0.11
help0.05
other0.02

returns {"choice": "refund"}

score

A level on your own scale: urgency, sentiment, risk.

How frustrated do they sound?

0.05
calm
0.18
worried
0.52
annoyed
0.25
angry

returns {"score": 1.97} (≈ annoyed)

noul · yes / no

Yes or no, as a probability: a complaint, an adverse event, spam.

Is it urgent?

returns {"noul": 0.71}

The question types in the API reference

Use cases

Where teams use a decision API

Hover or tap a card to see the kind of question Laya answers there.

  • Support ticket triage with a calibrated decision model

    Automate support ticket triage: one API call reads each ticket and returns intent, urgency, frustration and churn risk, with a confidence score per answer.

  • Email routing and threat triage with typed decisions

    Route inbound email to the right team automatically and flag spam, phishing and urgency in one call, with probabilities that decide what a person sees.

  • Intent detection with a calibrated decision model

    Detect what users want in chatbots, voice menus and search. Define intents per request, get calibrated probabilities and hand off to a person when unsure.

  • Content moderation with calibrated, typed decisions

    Moderate posts for toxicity, harassment, threats and spam in one call. Calibrated probabilities decide what is removed, sent to review or published.

  • Lead scoring from free text with calibrated confidence

    Score inbound leads from form fills, emails and CRM notes. Get fit, buying stage and persona in one API call, with calibrated confidence to prioritise sales.

  • Agent tool routing and model-tier selection with a decision model

    Route each AI agent step to the right tool or model tier with a calibrated decision model: difficulty, domain and tool choice in one fast, typed API call.

All use cases

Swiss data residency

Swiss-hosted inference. Nothing you send is ever stored.

Laya Studio answers your questions on GPUs located in Switzerland, keeps its account database in Zurich, and never writes the content of a request to disk. Turn on Swiss-only mode and a request is only ever answered on GPUs in Switzerland, never by a failover abroad. On the way it is handled in memory by our Cloudflare API gateway at the edge location nearest the caller, which can be outside Switzerland and stores none of the content.

  • GPUs in Switzerland. Our primary inference pool runs on dedicated GPUs located in Switzerland.
  • Swiss-only mode. One switch per workspace (or the x-laya-residency: ch header per request) and requests are only ever answered in Switzerland.
  • Zero content retention. The text and questions you send are processed in memory and discarded when the answer is returned.

A Jev alternative

The open model, speaking Jev’s protocol

TypeSafe Jev and Laya both answer typed questions without generating text. An existing Jev client works after two changes: the base URL and the key.

  • Faster and cheaper. about 120 ms end to end from Europe, and 15% below Jev’s list price per input token.
  • Open weights. Apache-2.0: run the same model yourself if you ever need to.
  • Where Jev is stronger. large label sets: on Banking77’s 77 intents it scores 0.870 against Laya’s 0.425.

Speed · one decision

Laya model · T4 GPU, in-process32.8–39.5 ms
Laya Studio · from Europe, end to end~120 ms
TypeSafe Jev · p50 over the internet236–276 ms

Not like-for-like: the first is GPU time in the process; the others include the network. Scale 0–300 ms.

Price · per 1M input tokens, same unit

Laya Studio$0.0357
TypeSafe Jev$0.042

15% less at every message length: both bill the tokens read.

Openness

  • Model weightsLaya open · Jev closed
  • Run it yourselfLaya yes · Jev no
  • ProtocolLaya /v1/systemone · Jev /v1/systemone
  • 77-label tasks (Banking77)Laya 0.425 · Jev 0.870

For developers

A decision model built for the calls you make a million times a day

One POST, typed questions, calibrated probabilities. Copy a request and run it.

One forward pass

No tokens are generated, so latency is short and predictable: a warm request takes about 120 ms end to end from Europe.

Probabilities, not prose

Every answer is a distribution over its options. Threshold on it, route on it, escalate on it.

Cannot hallucinate a label

The model scores the options you wrote. It can be wrong; it cannot invent a label or a sentence.

100+ languages

Language detection routes each request to the English or multilingual checkpoint automatically.

Jev wire-compatible

Same /v1/systemone request and answer shape. Migrate by changing a base URL.

15% below Jev

$0.0357 per 1M input tokens, against Jev’s $0.042 per 1M input tokens. Same unit, lower price, and failed requests are free.

POST /v1/systemonebash
curl https://api.laya.studio/v1/systemone \
  -H "Authorization: Bearer lsk_live_…" \
  -H "Content-Type: application/json" \
  -d '{"state":{"message":"I was charged twice this month. Refund me or I cancel."},"questions":{"intent":{"type":"choice","instructions":"What does the customer want?","criteria":{"refund":"money back or a duplicate charge reversed","technical_help":"a bug or integration problem","cancellation":"wants to cancel","other":"anything else"}},"urgent":{"type":"noul","instructions":"Does the message communicate time pressure?"},"frustration":{"type":"score","instructions":"How frustrated does the customer sound?","criteria":["calm","concerned","annoyed","very angry"]}}}'

Read the docs What calibrated probabilities are Jev alternatives compared

Laya Studio products

One key, one balance, more than decisions

The same account, API key and credits run every Laya Studio product.

  • Laya Guard

    Check an agent’s tool call before it runs: allow, ask or block.

    $0.20 per 1k checks

  • Laya Agent

    Soon

    A small model specialised in tool use and agent steps.

    In training

Pricing

Priced per input token, 15% below Jev

Slide to your volume. $0.0357 per 1M input tokens — 15% below Jev. 6k free tokens to start, then credits or a monthly plan from $19.

10k100M

You pay for the input tokens the model reads: 1 credit = 1 input token, at $0.0357 per 1M. Each question reads the text once (one question per request here). Failed requests are free.

Laya Studio · Pay as you go

$9.46/ month

265M input tokens · $0.0000095 per request

Jev at its list price ($0.042 per 1M input tokens): $11 / month · $0.000011 per request. 15% below Jev.

Every new workspace starts with 6k free tokens.

See all plans

FAQ

Questions, answered

What is Laya Studio?
A hosted API for Laya, the open-source System 1 decision model from Convai Innovations. You send a state (text or JSON) and typed questions; you get answers with calibrated probabilities in one forward pass. Laya Studio is an independent service and is not affiliated with Convai Innovations or TypeSafe.
What is a decision API, in plain words?
You send a piece of text, such as an email, a review or a patient message, together with the questions you need answered: what does this person want, is it urgent, how upset are they. The API answers each question with a probability instead of writing prose, so your software can act on the confident answers and hand the unsure ones to a person.
Is it compatible with TypeSafe Jev? Is it a Jev alternative?
Yes. Laya answers the same /v1/systemone request shape Jev uses — choice, score and noul questions with the same answer fields — so an existing Jev client works after you change its base URL to https://api.laya.studio and swap the key. Accuracy and confidence semantics differ; re-check your thresholds.
What does “calibrated probabilities” mean?
A probability is calibrated when answers given at 80% turn out right about 80% of the time. Laya is trained with proper scoring rules; its raw scores are over-confident as shipped (mean ECE 0.466), and fitting one temperature per question type on held-out data brings the mean calibration error to 0.081, according to its model card.
Can I send patient messages or other medical data?
No retention plus Swiss processing makes Laya Studio a fit for sensitive text such as patient messages, clinical intake notes, HR cases or financial correspondence — the kind of data that should not sit in a US AI provider’s logs. Our primary inference pool runs on GPUs in Switzerland, and with Swiss-only mode switched on a request is only ever answered there. Designed to support compliance with the Swiss Federal Act on Data Protection (nFADP, in force since 1 September 2023) and the EU GDPR. You remain responsible for your legal basis to process personal and health data. Laya Studio holds no formal certification (such as ISO 27001) today and does not sign HIPAA BAAs.
How is it priced?
Per input token, like Jev, but 15% cheaper: $0.0357 per 1M input tokens against Jev’s $0.042 per 1M input tokens. 1 credit = 1 input token, the tokens the model actually reads. Every new workspace gets 6k free tokens; after that you buy credits or pick a monthly plan from $19. Failed requests are never billed.
When should I not use Laya?
When the task needs generated text, multi-step reasoning, or a very large label set (Laya scores 0.425 on the 77-label Banking77 benchmark versus 0.870 for Jev). Laya is built for fast, well-defined decisions with a probability you can threshold on.
Do you store my data?
No. States and questions are processed in memory and discarded. We keep request metadata — time, status, question count, latency — for 30 days for billing and debugging.
Which languages are supported?
English runs on a ModernBERT-large checkpoint; 100+ other languages run on an mmBERT-base checkpoint. Routing between them is automatic, or you can pin one with the "model" field or pass a "lang" hint.

Start with 6k free tokens

Create a key, paste the curl, and have calibrated answers in under two minutes.