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-local-serve
yyong-brs
Runs Laya locally with Python, TypeScript, and integrations for serving and decision workflows
laya-on-aws-lambda
gunnargrosch
Deploys Laya as a Jev-compatible decision API on AWS Lambda using TypeScript or Python
jev-laya-form-builder
slamer59
Builds forms by letting hosted Jev or local Laya choose suitable input components
decide.js
asertyui1
Provides a typed SDK and CLI for routing decisions across Jev, Laya, local models, and offline heuristics
laya-studio
ewrogers
Provides a local web workspace and Jev-compatible API for trying Laya decisions
laya-project
wjesus374
A local Laya decision service with a FastAPI backend, SQLite storage and React dashboard
@molecule/api-ai-decisions-laya
vialoh
Connects molecule.dev to a self-hosted Laya model for typed choice, score and yes/no decisions
@molecule/api-ai-decisions
vialoh
Defines a provider interface for typed AI decisions, with Laya as a supported backend
@banh-dev/laya
banh-kevin
Native Laya ONNX inference package for the Banh workflow CLI
laya-api
MIYA2024
Serves a multilingual Laya typed-decision API on ZeroGPU
laya-js
desplega-ai
A TypeScript runtime and Hono server load ONNX Laya checkpoints and answer typed decision questions
spring-laya
pgovindraj
Tracks planned Spring support for the Laya model in spring-ai-typesafe
layaas-oci
acedergren
Deploys a pinned multilingual Laya decision API as a private CPU service on Oracle Cloud
laya-api
gugaucb
Serves Laya and Laya-MLX models through OpenAI- and Anthropic-compatible APIs
laya-playground
adyoi
Provides a FastAPI playground for Laya typed decisions with redaction and guardrails
laya-system-one-client
kyawzawwin88
Chrome extension for sending Laya decision requests and viewing typed responses
litellm-laya-demo
amkhrjee
Routes LiteLLM requests by complexity scores produced by Laya
sys1rust
kgarg2468
A Rust and MLX service runs Laya decision models locally and exposes the System 1 API
docker-ai-router
Gio53
OpenAI-compatible proxy that uses Laya difficulty scores to route requests between two LLM APIs
laya-fontaneros
doiranbl
Runs Laya's official HTTP server for typed decisions in a Docker space
trick-laya
beginbotbot
Serves Laya through an API compatible with TypeSafe Jev system-one requests
laya-hybrid-harness
Ra77Data
Runs a local Laya decision model and delegates uncertain cases to a cloud service
wagtail-laya
ottoreimers
Adds Wagtail editor buttons for Laya-based page tagging and rating
laya-ggml
liujp
Implements a C inference engine and HTTP service for the Laya decision model
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