Studio
Inspect and test your application's AI capabilities from the same ASP.NET Core host.
Studio is Runiq's embedded developer interface. It shows the components registered by your application and lets you investigate their behavior where they run.
Start with the question you need to answer
| Area | What to inspect |
|---|---|
| Agents | Instructions, attached capabilities, and a conversation in the Playground. |
| Tools | Input contracts and direct tool execution. |
| RAG | Index readiness, ingestion, and search observations during an agent run. |
| MCP | Discovered tools and local method execution. |
| Workflows | Registered steps, transitions, and execution outcomes. |
Studio reflects host registrations. Define agents, indexes, and workflows in application code; use the UI to inspect and test them.
Enable it in your host
Install Runiq.AI.Core, register the host services, and choose a Studio access mode. The default URL path is /runiq.
Studio does not need a separate deployment. Its requests use the running application's services, so a tool test can perform real application actions.
Inspect the right evidence
A successful tool call establishes that its tested input worked. An index marked ready establishes that content is available. Neither alone establishes that an agent's final answer is correct.
Review inputs, intermediate outcomes, and returned content together. MCP transport connectivity requires a separate client check.
Choose who can use it
Studio uses the host's authenticated user and roles. Configure an explicit access mode and keep middleware ordering consistent with your application.