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-docker
moecly
Docker Compose setup for running a Laya server
laya-mcp-server
carl0s
An MCP server and REST endpoint expose Laya for structured text and JSON decisions
laya-local-http-server
ratheesh-aot
Serves the Laya typed-decision model through a local HTTP API using MLX or PyTorch
dev
phix
Hardens and rebrands Laya as a local typed-decision engine with server and MCP support
Sent1nel
srinath1505
A guardrail SDK and API routes policy decisions through hosted Jev or self-hosted Laya
xcrystal
dgu0323
Scores cryptocurrency relevance and market signals in X posts with a local Laya server
laya-service
manul-audio
Wraps Laya predictions in a FastAPI service for Paperclip agent decisions
laya-ui
bharath-ui1027
Provides a multilingual Laya decision engine with UI components and optional serving integrations
laya-image
muck-stump
Provides a container image for deploying Laya on AMD-accelerated OpenShift
laya-docker
beremaran
A Docker image runs Laya as a GPU-backed, Jev-compatible HTTP server
laya-web-app
meossistant
Provides an offline web runtime for Laya with OpenVINO and PyTorch backends
laya-local-system
h7mei
Serves local Laya decisions through a web UI and Jev-compatible HTTP API
decisionsmith
izam-mohammed
Uses LLM teachers to generate data for fine-tuning Jev and Laya decision models
@mokei/system-one-client
paul_lecam
TypeScript System One client that works with a local laya-serve backend
@plumbus/ai-decision-laya
GitHub Actions
Provides a self-hosted Laya typed-decision adapter and Python reference service for Plumbus
@zatsepin/jigor
zatsepin
Offers a CLI and HTTP gateway for local ONNX Laya and von models and remote Jev decisions
laya-decision-lab
KGFCode
Demonstrates Laya text classification, scoring, and probability analysis with an API and MCP service
laya-triage
Mezahir2025
Provides a Laya-based message triage API for Make.com
laya_api
Anuragggggggg
Serves Laya typed-decision endpoints for generic decisions and candidate routing
laya-router
naufalacksaa
Hugging Face Space that serves Laya's /v1/systemone API with a small Gradio page
laya-server
MalikAwais11
Serves BudgetMate decision requests through a Laya API and provides a health endpoint
Laya-demo
robynsd
Provides an API demo for Laya typed decisions without text generation
NLaya
ljfio
Ports Laya typed-decision models to .NET with TorchSharp and ONNX Runtime
semantic-operators
jasonduncan
Provides Python, CLI, and MCP interfaces for typed judgments using Laya and 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