Policy first
Workspace rules constrain providers, models and external processing before a route is selected.
Yasnora AI / Capabilities
YASNORA AI / YOUR WORK
Let the task guide the eligible route.
Yasnora Auto selects among model routes allowed by server policy, task requirements and available capacity. Keep data boundaries ahead of convenience.
FROM TASK TO RESULT
Practical capabilities
Task requirements
Capabilities and context requirements help determine which approved route can handle the request.
Explainable limits
An unavailable eligible route should return a clear failure instead of silently widening access.
STEP BY STEP
A clear working process
Start with a small example. Clarify requirements and review the result before using it.
- 01
Describe the task
Provide the necessary context and expected output.
- 02
Apply workspace rules
Use the processing mode permitted for the material.
- 03
Run the request
Routing considers only eligible configured providers.
- 04
Review the outcome
Inspect limitations and retry with appropriate scope when needed.
EXAMPLE WORKFLOW
An illustrative task
An illustrative example using fictional data. It demonstrates an approach, not a real customer result.
Summarize a permitted internal document under a local-only policy.
Possible result structure
Evaluate policy → find an eligible local route → produce a summary, or report that no suitable route is available. External fallback is not implied.
How should I start?
Provide the necessary context and expected output.
What should I check before using the result?
Inspect limitations and retry with appropriate scope when needed.
What access and limits apply?
Routing cannot create a capability absent from the configured providers. Actual provider availability and deployment policies require environment-specific verification.
EXPLORE FURTHER
Related capabilities and reading
START WITH ONE TASK
Take your next step with Yasnora AI.
Guest chat needs no registration. Advanced capabilities depend on plan and configuration.