Hands-on tutorials
Build a complete LiyaEngine capability, step by step.
Follow practical paths that connect domain design, knowledge grounding, intent contracts, API calls, and operating evidence.
POST /v1/rundomainintentinputPublished tutorials
Choose a build path and leave with working context.
These tutorials are backed by complete guides in the documentation and focus on the parts developers need to implement.
Recommended sequence
Learn from contract to evidence.
The shortest path to understanding LiyaEngine is to build one small capability through its full lifecycle.
Create a domain
Establish the tenant-owned boundary and shared behavior.
Define an intent
Set the request and response contract the application will call.
Run a request
Use the dashboard or a code snippet with an API key.
Inspect the trace
Review retrieval, model, policy, latency, token, and cost context.
Operating principles
Make the production boundary understandable.
Strong platform UX makes ownership, behavior, controls, and evidence visible to the people responsible for the capability.
Bring a test workspace
Use your own domain for production design; sample domains remain useful for learning.
Keep credentials private
Use environment variables for API keys and never commit secrets to source control.
Iterate with evidence
Use test responses and traces to improve schemas, instructions, grounding, and policy.
Questions
Useful context before you build.
Which tutorial should I start with?+
Start with the docs chat widget for a visible end-to-end result, or the RAG pipeline if knowledge grounding is your primary goal.
Do tutorials use sample domains?+
Some learning material may use examples, but production implementations should use tenant-created domains, intents, and knowledge.
Can I test without writing code?+
Yes. The dashboard testing experience supports interactive requests, while code snippets remain available for developer workflows.
Build the first end-to-end capability.
Start with the quickstart, then use a tutorial to add the production behavior your product needs.