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
Laya
rkvishwa
Provides a local playground for composing queries and calling a self-hosted Laya server
laya-shim
bunkerlab-net
Serves Laya or Laya-MLX behind TypeSafe's System One API route
laya-docker
hrodic
Packages the Laya decision model as an offline Docker service using ONNX Runtime
pixelkit-laya
PixelKit-Labs
Provides local typed-decision APIs and ONNX inference adapters for TypeScript and React Native
n8n-nodes-layahost
Negmus
n8n community node for layahost: Laya and Clef decisions, flows and moderation in n8n workflows
jev-mcp
nik1tsyganov
MCP stdio servers expose TypeSafe Jev and a separate local Laya decision model
open-laya
skorotkiewicz
Provides a local HTTP API and MCP tools for Laya decisions
maclaya
jannisleifeld
Serves local Laya models on Apple Silicon through a Jev-compatible API with a dashboard and playground
laya-mlx-server
tankerwng2
Serves laya-mlx over HTTP using the Jev protocol and exposes an MCP interface
laya
HENILCHOPRA
Provides a multilingual, non-autoregressive model for typed decisions and optional serving integrations
laya-workflow
oliveagle
Ports a workflow engine to Rust and includes an inference crate that serves the Laya model
layajev
openbear-it
Serves Laya through a Jev-compatible HTTP API with CPU-only and multi-architecture container support
laya-js
abhimanyupandian
Packages Laya for local inference in browsers and Node.js using ONNX Runtime
workwe-laya
WorkWeonline
Provides a multilingual System 1 decision engine with typed outputs and optional serving and integration extras
laya-node-server
localhost-anon
A fully offline Node.js server and playground runs Laya through ONNX Runtime
fast-typed-classifier
navneetlal
A Python gRPC service classifies inputs with Laya's typed-decision models
laya-http-client
angelxmoreno
Provides a typed TypeScript client for Laya's HTTP protocol, with an MLX bridge sidecar
statim
BEKO2210
A native C++ engine that runs Laya checkpoints and serves the Jev/Laya decision protocol
qa-intent
zjarlin
A Rust CLI that generates QA banks and compiles them into Laya/Jev decision requests
EmailDetective
kaicao
Classifies messages as phishing or legitimate with Laya in an Agno agent served locally
laya-node
felipenmoura
A Node.js wrapper runs Laya as an authenticated Express classification server
Tiyakaloud
herveyyy
A Python server uses Laya and ModernBERT for support triage, classification, scoring, and routing
laya-play
teochenglim
Docker images package Laya’s built-in HTTP server for REST-based typed decisions
laya-server
criguex
A local Jev-compatible server runs Laya and can cascade uncertain decisions to Jev
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