Building and Testing Agents
Agents
Agents allow you to build the backend of your generative AI application. You can pick from a library of agents or create your own with your own models and data sets. The playground allows you to test the output of your agent against different prompts. The battleground allows you to test agents against each other to decide which one works best for your use case.
Before creating a agent, ensure that you have added at least one model and data source to your project. For more information, visit our section called “Model Lifecycle Management”.
Creating a New Agent
To create a new Agent:
- Select the Project you want to create your Agent in.
- Select the Agents tab.
- Validate that you have added at least one Model and one Data Source to your Model Library and Data Sources.
- Select “New Agent”.
- Give the Agent a name in the top left.
- Drag and drop nodes from the left side onto the canvas that you would like to use in your Agent.
- Use the line drawer to connect the objects together.
- Click “Save changes” or “Publish” to save your agent.
Test your agent in Agent Studio
You can now test your agent directly inside Agent Studio.
No more switching back and forth to a separate Playground while you’re iterating on your flow.
What you can do
- Inline Test mode – Chat with your agent without leaving Agent Studio.
- Playground Compare mode – Open the latest Draft and Published versions side by side to compare their behavior.
Both options live in the center-left controls on the Agent Studio canvas.
Inline Test mode (inside Agent Studio)
Inline Test mode lets you build, test, and refine in one place.
How it works
- Open your agent in Agent Studio.
- In the center-left canvas controls, click Playground.
- A Playground panel opens on the left with a chat interface.
- Type a message (for example, a realistic user input) and send it.
- Watch how your agent runs through the steps on the canvas and returns a response.
The inline Playground uses the current configuration of your agent on the canvas, so every change you make is immediately testable.
When to use it
Use Inline Test mode when you want to:
- Quickly validate a single flow or prompt change.
- Tweak steps, retry, and iterate in a tight loop.
- Stay in a focused build environment without switching screens.
Playground Compare mode (Draft vs Published)
The original Playground Compare mode is still available when you need a more formal comparison.
What it does
Playground Compare mode:
- Opens your latest Draft and Published versions side by side.
- Lets you send the same input to both versions.
- Makes it easy to see how changes to prompts, tools, or flows impact responses.
How to open Compare mode
- Open your agent in Agent Studio.
- In the center-left canvas controls, click Compare in Playground.
- The Playground opens with two panes:
- Left: Latest Draft version
- Right: Published version
- Enter a message and compare how each version responds.
Editing a Agent
To edit a Agent:
- Open the agent.
- Make changes on the canvas.
- Click “Save changes” or “Publish” to save your agent.
Debugging a Agent
To debug a Agent:
- Test the Agent on the playground
- Click the View Logs next to the output while testing, or navgiate to the Agent Executions feed on the left-side navigation and click on the Agent execution you are debugging.
- Review the Logs for errors.
Using Your Agent
To use your agent in your application:
- From the top navigation in Agent canvas, click the Settings icon.
- Select "Interfaces".
- Click "View API Info" next to the API interface.
- The API endpoint for the agent will appear.
- The headers of your API call should be:
- Content-Type: application/json
- X-API-Key: YOUR_API_KEY
- View the API Documentation for the body of the request.
Need other ways to use your agent? See Managing Agent Interfaces for Airia Catalog, Chat Widget, and other interface options.
To Generate Your API Key
You can generate an API key from the agent's interfaces panel — click View API Keys next to the API interface — or from Settings → Developer → API Keys.
Either way you will name the key, set the project scope, and copy the key value before saving it. The full key is only shown once.
API keys come in two kinds: one that acts as you, and one that acts as a standalone service account with its own roles. For production integrations the second is usually the right choice. See API Keys for the difference, the full create flow, and how keys behave when their creator leaves.
For complete interface setup guidance, see Managing Agent Interfaces.