Hosted Laya API
Laya is open weights, so you can always run it yourself. A hosted API makes sense when you do not want to run and patch a model server, when your traffic is small or spiky, or when you want to compare Laya with other decision models before committing. This page lists the options and what to check.
419 projects
kime
tamnd
A Rust inference engine and HTTP server runs Laya checkpoints across CPU, CUDA, and Apple GPUs
laya-console
biyyl234
Provides a local web console and REST API for Laya inference and intent classification
laya-studio-node
ajayjha1
Provides a Node.js and TypeScript toolkit for Laya classification, routing, CLI, and MCP use
laya-decision-api
bmw8080
An HTTP service wraps local Laya with OpenAPI documentation and Java, TypeScript, and Python SDKs
SystemOneSharp
pinkroosterai
Provides a .NET client for Jev and Jev-compatible local Laya servers
laya-pi
trinacria-tech
Runs Laya decision APIs and demos on a Raspberry Pi 4 using ONNX Runtime or PyTorch
laya-agent
inboxxobni
Runs Laya typed decisions locally on Apple Silicon and provides an HTTP server and agent integrations
laya-rk3588-turingpi-rk1
elepedus
Runs Laya inference on RK3588 Turing Pi RK1 modules through Mali GPU and Rockchip NPU backends
LayaOnnx
dot182
Wraps exported Laya ONNX checkpoints in a C# interface using ONNX Runtime
laya-decision-gateway
harshad-jadav
Serves Laya model decisions through a documented API gateway
Laya-Dockerized
sseeyyeedd
A local FastAPI service runs the multilingual Laya decision model and exposes prediction endpoints
laya-router
Gjusev
Routes prompts between inexpensive and frontier models through an OpenAI-compatible proxy using Laya
sys1rust
krishhgg
Runs Laya decision models on Apple Silicon with a Rust and MLX server compatible with the upstream API
Laya-Go-Launcher
Ling0727-ai
Loads Laya models and launches inference services through TensorRT or ONNX Runtime
mesh-decisions-playground
michaelneale
Provides a local web interface for making Laya decisions through Mesh LLM
RLaya
DaragonTech
A Rust binding runs Laya decisions in-process through LibLayaX
laya-engine
devinblaze
A Gradio API and interface for multilingual Laya decisions
edge-decision-laya-system1-demo
skdwriting
Demonstrates low-latency edge decisions using the Laya System 1 model and safety guardrails
laya_dart
lohanidamodar
Serves the Laya decision model through a Jev-compatible HTTP API
laya-mlx-http
noahwaldner
Serves laya-mlx decisions over HTTP and provides a Vercel AI SDK adapter
browser-laya
wexare-ai
Runs the Laya decision model in browsers using WebGPU or ONNX Runtime Web
dsh-router-laya-deploy
kaijin1448
Deploys and patches a local Laya decision service and its OpenCode integration on Windows
laya-ort
Fruank4
Runs Laya typed decisions on Linux x86_64 using ONNX Runtime
laya-mlx-jev-endpoint
rezhajulio
Serves laya-mlx through a FastAPI endpoint compatible with the JEV decision API
Disclosure: layahost is run by the same team as laya.tools. It is listed first for that reason, not as a ranking.
Self-host or hosted?
Self-hosting is the better fit when text must not leave your machines, when volume is high and steady so that your own hardware is cheapest per call, or when you need on-device latency. The API servers page covers laya-serve, ollaya, Docker and native servers, and the run-locally guide covers Python, Mac, Node.js and CPU setups.
Check the hardware first. laya-cpu-benchmark concluded that a realistic CPU call is 0.3 to 2 seconds, and the Railway template reports about 0.2 to 0.9 s per call on CPU, with around 3.4 GB of memory for both checkpoints. Without a GPU or an Apple Silicon Mac, a self-hosted server can be slower than a hosted one.
A hosted API is the better fit when you do not want to operate a model server, when traffic is low or bursty, or when you want features around the model, such as templates, test sets or other models on the same endpoint.
Hosted options
Details are from each service's site, checked on 2026-10-14. Neither is affiliated with Convai Innovations or TypeSafe.
layahost
- Models: Laya (
laya-english,laya-multilingual) on its own servers in Helsinki. Cloudflare's open Clef and Clef-flash on the same API, answered on Cloudflare's Workers AI GPUs. - API: the Jev-compatible
POST /v1/systemone, and a simpler/v1/decidewith ready templates: moderation, spam, support_intent, routing, sentiment, priority, prompt_injection, pii and language. - Tools: test sets in the console to compare models on your own labelled data, decision flows built in a visual editor, an MCP server, an n8n node (
n8n-nodes-layahost) and a drop-in for Google's Perspective API. - Pricing: Laya per decision (one answered question), the same whatever the text length. Clef per input token. New accounts get $1 of credit after email verification, with no card.
- layahost.com · migrating from Jev
Laya Studio
- Models: Laya's English and multilingual checkpoints, routed automatically.
- Location: GPUs in Switzerland and an account database in Zurich. A Swiss-only mode keeps requests from failing over abroad. The site says request content is not stored and request metadata is kept for 30 days.
- API:
POST /v1/systemoneatapi.laya.studio. - Pricing: per input token, like Jev. New workspaces start with 6k free tokens.
- laya.studio
Railway template
The Railway template is a middle way: a one-click deploy of a Jev-compatible Laya server into your own Railway account. You pay Railway for the machine and your text goes only to your own service, but running and updating it is still your job. Its page says a Hobby or Pro plan is needed for the memory.
What to check
- Data location. Where the model runs, where accounts are stored, whether request text is kept, and whether a failover can move a request to another country. On layahost, Laya and Clef run in different places.
- Pricing model. Per-decision pricing does not depend on text length, so a long email costs the same as a short one, but three questions in one request count as three decisions. Per-token pricing, which Jev also uses, grows with the length of the text. Price both with your real message length and questions per request.
- Jev compatibility. Both hosted services accept
/v1/systemoneand say an existing Jev client works after a base-URL and key change (layahost documents this for the official TypeSafe SDKs). The answers still come from Laya, so a confidence threshold tuned on Jev does not transfer. See the differences on the API servers page. - Latency. The network adds to the model's own time. Laya Studio reports about 120 ms end to end from Europe for a warm request, and layahost lists about 0.1 s for Laya and 0.4 to 1 s for the Clef models. Measure from your own region.
- Accuracy. Hosting does not change the model. Independent benchmarks put base Laya behind Jev and the larger open alternatives on hard tasks (see the benchmark section there, and Laya benchmarks for the model card's own numbers). Run a few hundred of your own labelled examples before you move production traffic.
More ways to use Laya