What is layahost?
layahost is a hosted API for typed decisions. You send a piece of text together with a question that has a fixed set of answers — a choice, a yes/no, or a score — and you get back the chosen answer plus a probability for every option, returned as JSON your code can branch on directly. Instead of generating free-form text you then have to parse, layahost returns only the options you define, each with a confidence value.
It implements the Jev System One API wire format, which means the official Jev SDKs work after you change the base URL and the key. Pricing is flat and prepaid at $5 per million decisions, and the service is hosted in the EU.
Who it's for
- Platform and community teams — who need to hold back insults, harassment and threats before comments are published.
- Support and operations teams — who want to know what a customer wants, and which department should handle it, before anyone opens the ticket.
- Developers building on Jev — who already use the Jev SDKs and want a compatible endpoint without rewriting their integration.
Key features
Typed decisions with probabilities
Every request returns one of your defined options along with a probability for each, so your code can branch on a value rather than parse prose. Answers come back as JSON.
Jev-compatible wire format
layahost speaks the same /v1/systemone format, with the same question types, answers and errors. The official Jev SDKs work as they are once you point them at layahost and use a layahost key.
Built-in use cases
The API covers content moderation, spam and scam filtering, support triage, ticket routing, priority and escalation, sentiment, and language detection across 35 languages.
Custom models
For your own labels — product categories, internal teams or policy rules — a private Laya checkpoint can be fine-tuned on your labelled examples and served on the same API.
What stands out
Decisions, not text.
That framing captures the product's real edge: it doesn't try to be a general text generator, it returns a bounded answer with a confidence score you can act on. Because only the options you define can come back, there's no malformed output to handle. And since it follows the Jev wire format, adopting it is largely a matter of changing a base URL and a key.
Worth checking out if…
You want moderation, routing, intent or scoring decisions from a single API call rather than a pipeline of prompts and parsers. It's also worth a look if you're already on the Jev SDKs and want a compatible endpoint, or if you need your own labels served from a private model on the same interface.
