stiermid/laya-serveArchived
User repository on GitHub
Jev-compatible HTTP server for Laya System One decision models
- Forks
- 0
- Last pushed
- Updated Sep 2026
Repo stats from the GitHub API, cached Oct 2026.Homepage
CommunityJev Demos & Experiments
Laya Serve
Archived. A Jev-compatible HTTP server that lets any Jev client run against local Laya weights instead of the TypeSafe API, serving POST /v1/systemone with typed choice, score and noul answers. Upstream laya now ships this natively.
- Stars
- 2
- Language
- Python
- License
- APACHE-2.0
- Published by
- Community
- Author
- stiermid
- Last verified
- Oct 2026
About this project
Jev-compatible HTTP server for Laya System One decision models. Point any Jev client at this server and get typed choice / score / noul answers from local Laya weights instead of the TypeSafe API. Errors use {"error": {"message", "field"}} with Jev status codes (401 bad key, 422 validation, 429 rate limit with a Retry-After header when LAYASERVERATELIMITPERMINUTE > 0, 529 transient overload with a Retry-After header, 500 unexpected backend failure with internals logged server-side).
Quoted from the project's README. Read the full README.
Works forJev for Classification
Used inJev for Software & DevTools
- Languages
- Python
Highlights
- Documented divergences from the hosted API: Laya's confidence is entropy-based, output_tokens is always 0, and choice criteria as a list is accepted leniently.
- Accepts jev-latest, jev-preview, jev-1.13.0, jev-1.13, laya, laya-latest and the serving model id, rejecting anything else with 422.
- A fake backend needs no weights at all and returns deterministic uniform answers, which is the path for CI.
- Error envelopes follow the Jev shape with 401, 422, 429 and 529, and Retry-After headers where a limit is set.
Watch out
This repository is deprecated and read-only, with no further releases; upstream laya ships Jev-compatible serving natively via pip install "laya[serve]" and the README says to uninstall this package first to avoid a script collision on the same laya-serve binary. The migration table documents real behavioural differences: this repo's GET /healthz becomes GET /health upstream with added loaded, revisions and device fields, GET /v1/models has no equivalent upstream, in-process 429 limiting becomes an admission bound returning 503 so you enforce 429 at the gateway, the fake backend is gone, and the strict caps here become 400/413/422 upstream with plain {"detail": ...} errors instead of the Jev error shape. The most important caveat for anyone still on this version is calibration: Laya computes confidence as 1 - H(p)/log(k) while Jev documents peak-based normalization, so the same probabilities produce different confidence values and thresholds must be fitted against Laya. Compatibility was verified against the docs and laya 0.3.x source, not against a live TypeSafe endpoint. Copy reviewed against the repository README on 2026-10-04, not from running it.
Questions about this entry
Short answers drawn from the linked project or page.
Use upstream instead. laya now ships Jev-compatible serving natively, so pip install "laya[serve]" gives you the same laya-serve binary and the same POST /v1/systemone endpoint. The README instructs you to uninstall this package first, because both ship a script with the same name. If you are pinned here, note the renames that will bite you: LAYA_SERVE_DEVICE and LAYA_SERVE_PRELOAD become LAYA_DEVICE and LAYA_PRELOAD with preloading on by default, LAYA_SERVE_API_KEY becomes LAYA_API_KEY, and there are new LAYA_MODELS, LAYA_THREADS and LAYA_MAX_CONCURRENT variables.
For the evaluation path, yes, which is the point of the compatibility work. Requests use the Jev shape, and responses contain exactly the Jev fields with Laya-only additions stripped: action is removed from every answer and confidence from noul answers. The model field echoes the serving checkpoint, the way Jev echoes its resolved version id. Validation mirrors Jev too: choice up to 255 options, score 2 to 10 levels, model required and non-empty questions, all 422. One leniency in your favour: choice criteria as a list is mapped to {label: None}, where Jev requires a map.
You get probabilities, but not the same confidence numbers, and that matters for thresholds. Laya computes confidence as an entropy-based 1 - H(p)/log(k) while Jev documents a peak-based normalization, so identical probability distributions can yield different confidence values. The README is explicit: calibrate thresholds against Laya, not against Jev. Also, output_tokens is always 0 because Laya never generates tokens and this layer does not invent counts, and the checkpoint still truncates per-question sequences at its own max_len.
Yes, set LAYA_SERVE_BACKEND=fake, which is in fact the default. It returns deterministic uniform answers and needs no weights, which makes it the path for API development and CI. For real weights, set LAYA_SERVE_BACKEND=laya and pass LAYA_SERVE_PRELOAD=true, which the README recommends for servers. Other knobs: LAYA_SERVE_DEVICE selects the Router device, LAYA_SERVE_MAX_LOADED caps resident checkpoints at one by default, and LAYA_SERVE_API_KEY plus a nonzero LAYA_SERVE_RATE_LIMIT_PER_MINUTE turn on bearer auth and rate limiting.
The upstream laya[serve], which now ships Jev-compatible serving natively: pip install "laya[serve]", same laya-serve binary and POST /v1/systemone. Uninstall laya-serve first to avoid the script collision. The migration also renames environment variables, for example LAYA_SERVE_DEVICE becomes LAYA_DEVICE and LAYA_SERVE_PRELOAD becomes LAYA_PRELOAD.
POST /v1/systemone for Jev-compatible evaluation, GET /v1/models listing the serving model and accepted aliases, and GET /healthz as a liveness probe that is not part of the Jev API. Errors use {"error": {"message", "field"}} with Jev status codes 401, 422, 429 with a Retry-After header, 529 and 500.
Laya uses an entropy-based confidence of 1 - H(p)/log(k), while Jev documents a peak-based normalization, so identical probabilities can yield different confidence values. Calibrate thresholds against Laya, not Jev.
More Jev resources like this
46GitHub stars
Open 150M encoder that reproduces the typed noul, choice, and score interface in one forward pass, trainable on a free GPU and runnable locally for nothing.
Jev Demos & Experiments#community#jevbest#catalog-import
941GitHub stars
Library that adds schema-guaranteed typed outputs to existing autoregressive LLMs without changing weights, served through SGLang or a hosted API.
Jev Demos & Experiments#community#jevbest#catalog-import
Community
TypeLLM/TypeLLMPython
TypeLLM/TypeLLMPython55GitHub stars
Toolkit that makes a model behind an OpenAI-compatible endpoint or running in-process answer typed choice, score, and yes/no questions from next-token probabilities in Jev API shape.
Jev Demos & Experiments#community#jevbest#catalog-import
Community
fidecastro/jevifyPython
fidecastro/jevifyPython164GitHub stars
End-to-end toolkit that synthesizes decision data, trains and calibrates candidate scorers, evaluates fixed splits, and serves Jev-compatible inference for interactive web decisions.
Jev Demos & Experiments#community#jevbest#catalog-import
Community
zwliJay/jev-forgePython
zwliJay/jev-forgePython63GitHub stars
Claude Code kit that guards PreToolUse calls with a free pre-filter plus one Jev question for ambiguous cases, and adds sub-agent sizing, rechecks, search, daemon speedups, and monitoring.
Jev Demos & Experiments#community#awesomejev#catalog-import
Community
jonathanavis96/jev-kitPython
jonathanavis96/jev-kitPython70GitHub stars
Self-hosted proxy that records typed decisions, distils them into small heads on a frozen encoder, and answers locally when confident.
Jev Demos & Experiments#community#jevbest#catalog-import
Community
bladedevoff/stuntdPython
bladedevoff/stuntdPythonFrom the Jev guides
Original write-ups on what this entry is for.
A game tick is a state plus a legal action list. How Clash Royale, Minecraft, and the earlier Mario, Pokémon, StarCraft, and drone loops ask Jev one step at a time.
Jev Demos & Experiments#gaming#agents#control
Read article
From the Jev community
Posts from builders shipping with Jev right now.