Turn product behavior into callable intents
Each intent can define input, output, instructions, knowledge, tools, memory, execution, and guardrails without forcing users into low-level model plumbing.
Explore the APILiyaEngine gives every team a clean API surface for domains, intents, agents, workflows, knowledge, and guardrails so AI features can move from demo to production with confidence.
legal-opsPOST01curl https://api.liyaengine.ai/v1/run \02 -H "Authorization: Bearer $LIYA_API_KEY" \03 -H "Content-Type: application/json" \04 -d '{05 "pack": "legal-ops",06 "intent": "contract-review",07 "input": { "message": "Flag risky renewal terms." }08 }'
{ "risk_level": "high", "citations": 2 }Define the business surface once, then expose schema-bound AI capabilities through clean API routes.
Built for teams across
Domains create the boundary. Intents expose the capability. LiyaEngine handles the runtime details that usually scatter across prototypes, scripts, and dashboards.
Each intent can define input, output, instructions, knowledge, tools, memory, execution, and guardrails without forcing users into low-level model plumbing.
Explore the API{
"summary": "string",
"risk_level": "low | medium | high",
"next_action": "string",
"citations": ["source_id"]
}Set the tenant-owned boundary for API identity, prompts, knowledge, and tools.
Define the callable capability that lives inside the domain.
Link existing collections without duplicating documents.
Test live calls, then inspect traces, cost, latency, and safety results.
POST /v1/runProduction AI needs more than a model call. LiyaEngine keeps behavior explicit, testable, and traceable across every tenant-owned capability.
Apply checks for sensitive data, unsafe actions, and domain-specific constraints.
Keep knowledge managed centrally while linking only what each domain needs.
Review changes, test behavior, and keep production calls aligned with the latest draft.
Teams use LiyaEngine to replace scattered model plumbing with callable, testable capabilities.
“LiyaEngine cut our AI feature development time from six weeks to three days. We called an intent and got structured, validated output back every time.”
“We connected our own knowledge base and defined our own intent schemas. Every response comes back validated against our schema.”
“We can finally see what every call costs and which model served it. Zero malformed outputs in production since we switched.”
LiyaEngine keeps sample domains available for testing, but production users create and manage their own domains, intents, agents, workflows, and knowledge base.