layaR runs Laya decision models locally from R. You ask typed questions about a piece of text or a record (pick one label, place it on a scale, or say yes/no) and get calibrated probabilities from a single forward pass. Nothing is generated, so there is nothing to parse and nothing to hallucinate.
It wraps Laya’s Rust port (laya-onnx) through extendr and runs on ONNX Runtime. No Python and no server are needed at prediction time.
Status: early development. Linux and macOS only for now; Windows is waiting on an upstream change (NandhaKishorM/laya#1505).
Installation
layaR builds from source and needs a Rust toolchain (rustc 1.85 or newer) and, on Linux, OpenSSL headers (libssl-dev / openssl-devel).
# install.packages("remotes")
remotes::install_github("gueyenono/layaR")Getting a model
layaR needs an ONNX export of a Laya checkpoint (1.3 to 1.6 GB each). laya_download_model() fetches one from gueyenono/laya-onnx, which holds ONNX exports of the three upstream checkpoints (unchanged weights, Apache-2.0):
laya_download_model("multilingual") # also "english" and "typed-decisions"
laya_models() # (paths shortened)
#> checkpoint installed path source layout size_gb
#> 1 multilingual TRUE ~/.cache/R/layaR/onnx/multilingual layaR fused 1.32
#> 2 english FALSE ~/.cache/R/layaR/onnx/english <NA> <NA> NA
#> 3 typed-decisions FALSE ~/.cache/R/layaR/onnx/typed-decisions <NA> <NA> NATo use an export you made yourself with the script from the Laya repository, import it instead:
pip install laya "torch>=2.9" onnx onnxscript onnxruntime transformers safetensors huggingface_hub
python laya-rust/tools/export_onnx.py --model multilingual --out ~/laya-exports
laya_import_model("~/laya-exports/multilingual", "multilingual")laya_model_root() explains where models live. A model exported for Laya’s Rust or TypeScript SDK (in ~/.cache/laya/onnx) is found too.
Quickstart
library(layaR)
questions <- laya_questions(
department = laya_choice(
"Which department should handle this request?",
billing = "invoices, payments, refunds",
technical = "bugs, outages, system errors",
sales = "pricing, new contracts",
other = "everything else"
),
urgency = laya_score("How urgent is this request?",
c("not urgent", "soon", "critical deadline or blocking issue")),
churn_risk = laya_noul("Does the customer say they will cancel or leave?")
)
state <- list(
subject = "Duplicate charge on invoice #4411",
body = "Hi, we were billed twice for March. Please refund the duplicate today or we will cancel our plan."
)
res <- laya_predict(state, questions)
res
#> <laya_result> laya-rl-agent · 3 answers · 235 input tokens
#> department choice billing p 1.00 confidence 1.00
#> urgency score 1.87 (0–2) confidence 0.64
#> churn_risk noul 0.88 → TRUE confidence 0.88
as.data.frame(res)
#> id type answer value confidence answer_confidence act_probability abstention
#> 1 department choice billing 1.0000 1.0000 1.0000 1 <NA>
#> 2 urgency score 1.87 1.8685 0.6371 0.8721 1 <NA>
#> 3 churn_risk noul TRUE 0.8782 0.8782 0.8782 1 <NA>The first call loads the model (a few seconds); later calls take a few hundred milliseconds on a CPU. Wording matters: asking whether the user “threatens” to cancel misses this ticket, while “says they will cancel” gets it (see vignette("writing-questions")).
The guides cover the rest: vignette("layaR") to get started, then writing questions, data frames and long documents, and models and performance. If you work with dplyr and tidyr, see Using layaR with the tidyverse.
Many states
tickets <- c("Refund my duplicate charge", "The login page crashes", "What does Pro cost?")
batch <- laya_predict_batch(tickets, questions)
as.data.frame(batch)Presets, abstention, long documents
laya_predict(list(message = "My payment failed twice"), laya_preset("triage"))
# Report "abstained" instead of trusting a low-confidence answer
laya_predict(state, questions, min_confidence = 0.8)
# Scan a document longer than the model's context window
laya_predict_long(contract_text, questions)A data frame in, answers out
tickets <- data.frame(
subject = c("Duplicate charge", "App crashes on login"),
body = c("We were billed twice. Refund it or we cancel.", "Since the update I can't log in.")
)
laya_annotate(tickets, questions, state = c("subject", "body"))
# adds department (a factor), urgency, churn_risk and a _confidence column for each
# a tibble in gives a tibble out, so it works inside a dplyr pipeline tooEmails and languages
state <- laya_email_state(subject = "Refund", body = raw_body, sender = "ana@example.com")
laya_predict(state, laya_preset("email"))
# Pick a checkpoint: the English one only reads English
laya_detect_language(c("Please refund me", "Me cobraron dos veces. \u00bfPueden devolverme el dinero?"))Sharing questions with Python
Question sets use the Python SDK’s format, so they move between languages:
laya_questions_to_json(questions, "questions.json")
questions <- as_laya_questions("questions.json")Errors
Every error has class laya_error and a specific laya_error_<kind>, so you can handle one kind on its own:
tryCatch(
laya_predict(state, questions, max_len = 32),
laya_error_no_markers = function(e) message("Options don't fit: ", conditionMessage(e))
)