Skip to content

armgit / laya

Public Imported from GitHub
0

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.

docs(serve): add marcreichel/laya-php client reference to self-hosting docs

Sarthak Pandeyeebab78bf67d
diff --git a/README.md b/README.md
index 4aadb0c4..1811bade 100644
--- a/README.md
+++ b/README.md
@@ -473,7 +473,7 @@ The hint only decides *English or not*: a code whose primary subtag is `en`, `en
wire protocol as TypeSafe's hosted Jev API. Laya's answer payload is already
schema-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
+the [`hs-jev`](https://github.com/getmissionctrl/hs-jev) Haskell client or the [`marcreichel/laya-php`](https://github.com/marcreichel/laya-php) PHP / Laravel SDK — just
needs its `baseUrl` repointed; nothing else changes.
```bash
diff --git a/docs/http-api.md b/docs/http-api.md
index a1bb894a..38478b60 100644
--- a/docs/http-api.md
+++ b/docs/http-api.md
@@ -1,7 +1,7 @@
# HTTP API
`laya-serve` exposes Laya over the TypeSafe Jev `/v1/systemone` wire protocol. A client written
-against Jev -- `hs-jev`, `typesafe-sdk`, or your own -- can point its base URL at this server and
+against Jev -- `hs-jev`, `typesafe-sdk`, [`marcreichel/laya-php`](https://github.com/marcreichel/laya-php) (PHP / Laravel), or your own -- can point its base URL at this server and
keep working: Laya's `predict()` output is already schema-compatible, and the server adds only the
HTTP surface: one decision route, a health probe, an optional bearer check and request limits.
diff --git a/laya/serve.py b/laya/serve.py
index ed08d39a..10a46723 100644
--- a/laya/serve.py
+++ b/laya/serve.py
@@ -3,7 +3,7 @@
Laya's ``predict()`` output is already schema-compatible with the Jev decision
API -- ``choice`` / ``score`` / ``noul`` answers and a ``{input_tokens,
output_tokens}`` usage block -- so a client written against Jev (for example the
-`hs-jev` Haskell client) can point its ``baseUrl`` at this server and keep
+`hs-jev` Haskell client or `marcreichel/laya-php` PHP SDK) can point its ``baseUrl`` at this server and keep
working unchanged. All this module adds is the HTTP surface Laya itself does not
ship: a ``POST /v1/systemone`` route, an optional bearer check, and a health
probe.