Solutions
Liya Engine ships as three production-ready solutions — Talent AI, Liya Chat, and Liya Support Intelligence — each built on the same domain-aware AI platform.
Liya Engine is the underlying platform. On top of it sit three product solutions, each pre-configured for a specific use case. You choose the solution that fits your workflow, connect it to your data, and deploy.
Available solutions
| Solution | Status | Best for |
|---|---|---|
| Talent AI | Live | Recruiting, HR, talent acquisition teams |
| Liya Chat | Live | Customer-facing chat, knowledge Q&A, help center deflection |
| Liya Support Intelligence | Beta | Support ops, agent assist, triage, QA |
How solutions relate to the platform
Every solution is a configured layer on the same Liya Engine core:
This means:
- API shape is consistent across all solutions — same auth, same
/v1/runendpoint, same session model - Configuration is shared — persona, BYOK, RAG settings, and data retention apply across solutions
- Knowledge base is per-domain — each solution draws from its own scoped knowledge sources
Which solution should I use?
Talent AI — if you are building a recruiting product, HR platform, or candidate experience tool and need AI that genuinely understands careers, job descriptions, and hiring decisions.
Liya Chat — if you need a grounded Q&A assistant that answers from your docs, knowledge base, or product content. Deploys as a website widget in one script tag.
Liya Support Intelligence — if you are building agent assist, triage automation, or QA workflows on top of a support operations stack.
Common implementation steps
Regardless of solution, every integration follows the same pattern:
- Create an account and get your API key
- Enable the relevant domain pack in the dashboard
- Upload your knowledge documents (
POST /dashboard/knowledge/upload) - Configure your persona and model strategy (
PATCH /dashboard/account/config) - Call the API (
POST /v1/run) or deploy the widget
See the solution-specific pages for exact request shapes and example workflows.