HunterAlphaHub
OpenRouter model reference Facts from the public catalogue, dated and labelled
Jev Laya Verified
2026-10-10

GitHub · Serving and API

marcreichel/laya-php

Putting a decision model behind a PHP or Laravel application without a token bill.

The repository's GitHub card, read on 2026-10-09

What it does

An SDK for Laya's typed decisions in PHP: describe the decision as a readonly class with enums, ints and bools, and the package asks the questions, reads the confidences and hydrates an instance — so a ticket can be routed or a renewal risk spotted without paying per token and without the text leaving the machine.

The repository's own description: “A Laravel-ready PHP SDK that turns Laya's typed decisions into typed PHP objects.”

How it works

It speaks the systemone wire format over whichever PSR-18 client is installed, pointed at laya-serve, Laya's Python HTTP server; each #[Ask] parameter becomes one typed question and the answers are hydrated back into the class. A built-in fake answers the same calls, which is what lets the unit tests run with no server and no key.

The repository, by the numbers

Stars
87
Forks
3
Language
PHP
Last push
2026-10-08

Read from the GitHub API on 2026-10-09. Stars and the last push move daily — quote them with the date, the way we do.

What we checked

  • the README's quickstart, the Triage code sample and the Laravel section, read 2026-10-09
  • the requirement line (PHP 8.4+) and the compose.yaml that pins upstream Laya to v0.4.0
  • the CI description: requests checked against TypeSafe's OpenAPI spec per change and weekly
  • the licence file and the GitHub metadata: 87 stars, 3 forks, last push 2026-10-08

What we did not check. We did not install the package, stand up laya-serve, or run a decision through it, so the coverage badge and the claim that any systemone server will do are the author's rather than ours.

Open the repository ↗All builds

Send us a link

A project built with Jev, a post, a video, a correction, a tip. We open the link, check it says what you said it says, and write the entry ourselves.

Required a link, and an email to reply to. Optional everything else.

Add context — all optional

One or two sentences about what it does, in your words. We write the entry ourselves.

Cost, latency, a benchmark — anything you measured. We attribute these to you.

We store what you type and email it to ourselves. No IP address, no user agent, no referrer — the same rule as the mailing list.

What happens to what you send →