Guides
The path is a ticket you can run, then the pitfall that bites that run. Three longer guides cover the hosted API itself: how a decide request is shaped, how credits and keys are metered, and how support triage uses the four typed answers plus the free confidence gate. The shorter notes below are the local-package pitfalls. Numbers in those notes are from the upstream README, the Hugging Face model card, or the Docker doc. Comparison tables stay on benchmarks. This site does not add a checkpoint, a score, or a routing rule that those sources do not state.
- Decide APIState, choice, score, and noul, the model aliases this gateway resolves, and the status codes it returns.
- Credits and keysThe monthly grant, prepaid packs, laya_ keys, rate limits, and what the usage ledger stores.
- Support triage in productionThe four support-triage questions, POST /v1/support/triage, and a confidence gate that does not spend tokens.
- Support triage toolRun the hosted support-triage tool, or call POST /v1/support/triage with a laya_ key.
- InstallPython 3.10 or newer, venv or uv, and the copy-ready pip command. /start opens this page.
- Router vs one checkpointRouter returns routing metadata. typed-decisions is not automatic. A local model path omits that object.
- Chinese routingHan text goes to the multilingual checkpoint. Score questions there have a position bias (issue #131).
- Calibrationconfidence is 1 minus normalized entropy. Gate on answer_confidence. The act head is not a signal.
- Fine-tune (RLCD)0.766 is laya-typed-decisions on the model card. The bases are 0.362 and 0.352. The notebook is the project’s RLCD loop.
- Serve with DockerCompose CPU and CUDA quickstart, then laya-serve on 127.0.0.1:8000. From the upstream Docker doc.
- Many labelsBanking77 at the default head budget. Shortlist, widen the budget, or split the question.
- Laya vs JevOfficial self-test and third-party cards stay in separate tables.