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-demo
mkhante
Provides a standalone Go server and client that embed native Laya inference
laya-api
moothz
Serves text and zero-shot image classification through a FastAPI backed by Laya and vision encoders
laya-delphi
jclr329-gmail-com
Delphi components connect to a local Laya server for inference, database analysis, evaluation, and fine-tuning
laya-service
FnSGit
Serves local Laya inference through a FastAPI endpoint compatible with the Jev protocol
laya_model
ranjithjunnu
Demonstrates a local PyTorch Laya decision service for classification and workflow planning
hybrid-classification-poc
zeachco
Provides a Python classification server with a TypeScript client that downloads and runs Laya
laya-claude-code-integration
danhnguyen-xiontechs
Installs and serves Laya locally on Windows, with an optional Claude Code MCP integration
locally-run-Convai-Laya-AI
basavaraj1997
Runs Convai Laya locally behind a REST API with interactive Swagger documentation
local-systemone
axiomantic
Provides a self-hosted System 1 decision daemon and MCP server with a native Laya backend
laya-api
Kibana21
A self-hosted HTTP API that serves Laya typed-decision checkpoints
zikai
jacobhausler
A Chinese idiom decision API offers Laya among its supported model adapters
laya
luigidemasi
Packages a configurable Laya decision API in a general-purpose container
laya
getlexora-ai
Deploys the open-source Laya decision model as a CPU service with a playground and test set
laya
bimlesharma
A Docker Compose stack that serves the Laya model through a self-hosted API
laya-scripts
minhquan2904
Python scripts for serving Laya on CPU and collecting encrypted request data
Fraudshield-Laya
23f3004075
A real-time fraud prevention engine with Laya and other decision-model backends
layastudio
Lu-cong-1
Provides a local visual workbench for testing, evaluating, and serving Laya decision models
laya_server
smarty-kiki
Serves a local Laya decision model through a Jev-compatible API on Apple Silicon
laya-serve
enlotec
Serves Laya typed decisions through REST and MCP endpoints
laya-api
polites-co-jp
Provides a signed relay API for Laya endpoints and a development chat client
laya-go-server
Djancyp
Serves Laya GGUF models through a local HTTP API built with Go and llama.cpp
pi-laya-classify
catanomad
Registers Laya classifier models in Pi through a self-hosted server and TypeScript client
layam
husien4
Hugging Face Space exposing a Laya Router REST endpoint with API-key auth
laya
mpjivdc
Provides a multilingual, non-autoregressive model for typed text decisions with Python and TypeScript interfaces
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