Non-autoregressive System 1 decision engine. Typed choice, score and yes/no decisions over any text in a single forward pass, in 100+ languages, with a router that picks the right checkpoint per request.
Python calibrationclassificationdecision-modelhuggingfacejevmodernbertmultilingualnlppythonpytorchroutingtyped-decisionszero-shot
docs(http-api): list laya-php, the PHP client that targets laya-serve
Yi-111-a656b1319b77d
diff --git a/README.md b/README.mdindex 9fba1026..7619ae70 100644--- a/README.md+++ b/README.md@@ -606,7 +606,8 @@ wire protocol as TypeSafe's hosted Jev API. Laya's answer payload is alreadyschema-identical to what Jev returns (`choice`/`score`/`noul` answers and a`{input_tokens, output_tokens}` usage block), so an existing Jev client — e.g.the [`hs-jev`](https://github.com/getmissionctrl/hs-jev) Haskell client — just-needs its `baseUrl` repointed; nothing else changes.+needs its `baseUrl` repointed; nothing else changes. A PHP client that targets+`laya-serve` rather than Jev also exists: [`marcreichel/laya-php`](https://github.com/marcreichel/laya-php).```bashpip install "laya[serve]" # adds fastapi + uvicorn + python-multipartdiff --git a/docs/http-api.md b/docs/http-api.mdindex 819307ce..99b6f973 100644--- a/docs/http-api.md+++ b/docs/http-api.md@@ -5,6 +5,11 @@ against Jev -- `hs-jev`, `typesafe-sdk`, or your own -- can point its base URL akeep working: Laya's `predict()` output is already schema-compatible, and the server adds only theHTTP surface: one decision route, a health probe, an optional bearer check and request limits.+A client that targets `laya-serve` rather than the Jev API exists for PHP:+[`marcreichel/laya-php`](https://github.com/marcreichel/laya-php) is a Composer SDK (PHP 8.4+)+that maps a class of enums and attributes onto questions and returns an instance, reads `GET /health`+for a deploy check, and ships a test fake so callers can unit-test without a running server.+```bashpip install "laya[serve]"laya-serve # http://0.0.0.0:8000