Get Started
The two surfaces of the builder, and how to find your way around.
Each agent in the Qore Agent Builder is a dedicated record. What you configure here — instructions, knowledge, tools, triggers, integrations, credentials, security controls — becomes how the agent behaves at runtime, inside whatever application embeds it.
The two surfaces
The Builder Canvas is the visual workspace. It shows the agent's connected knowledge, skills, triggers, and configuration as a diagram, so you can see at a glance how the agent is wired — which connectors are attached, what knowledge it can reach.
The builder chat is on the left. Describe changes to the agent there, and the builder applies them. To chat with the agent itself, select Try Agent in the canvas header: the Agent Playground opens in a new tab.
A header across the top carries the global actions: the Overview and Flow tabs, the version selector, Integrate Agent, Export Agent, Agent Config, and Try Agent. See The headers.
Start an agent
Create New Agent reads Describe the task. I'll build the agent to do it. Describe the agent in Describe the agent you want to build… (select + to attach files), or select a template chip below the prompt, such as Collections Agent. Not starting from a prompt? Two links sit below the chips:
Import an existing agent — bring in an agent package exported from Platform: a ZIP file up to 50 MB. Select Next to continue. See Export Agent for what an import restores.
Build from your IDE — Connect to coding agents (MCP) connects your agents to an MCP-capable coding agent, such as Claude Code or Cursor, with an API key.
Connect to coding agents (MCP)
The dialog lists three MCP servers, each with an example command for Claude Code:
Agent Builder MCP
Create, configure, and manage agents.
Knowledge MCP
Build datasets, ingest documents, and query the knowledge attached to your agents.
Agent Executor MCP
Interact with your deployed agents by invoking them through the trigger API. An Executor version menu, such as 1.4, sets the version in the command.
Every request needs the x-platform-key header. Under API keys, select + Add Key to create a key. A key is valid only for the current workspace and account, and you can revoke it at any time. Before you've made one, the list reads No keys yet.
My Agents
My Agents, below the prompt, lists your agents with their name, description, and when each was last updated. Narrow the list with Search agent…, and switch between the list and grid layouts. The ▷ icon on a row is Try Agent.
Each agent's ••• menu has:
Export Agent — opens the same Export Agent Package dialog as the canvas header. See Export Agent.
Executor Version — choose the runtime version. The current one is ticked, and 1.0 is marked Deprecated. See Runtime & Versioning.
Delete Agent.
For every task in one place, see Create an agent.
Finding the setting you need
The builder's pages are organized by the order you work in, not by the order the settings panel happens to list them.
Define the agent — identity, instructions, behavior, runtime, skills, MCP tools, connectors, knowledge, triggers, secrets
Validate it against scored datasets before anyone depends on it
Ship it into your product, with authentication, domain, PII, and guardrail controls
Watch production behavior and feed what you learn back into Build
If you're looking for one specific screen, the Overview lists every page under its stage.
Common paths
Go live in your product — Integrate Agent and Access & Security
Improve quality before release — Evals, Instructions, Skills & Capabilities, and Guardrails (Beta)
Improve quality after release — Monitoring, Online-Eval, and Reinforcement Learnings
Move an agent between environments — Export Agent, Secrets & Variables, and Runtime & Versioning
Why the configuration matters
What you set here becomes the agent's runtime behavior. Model selection, response format, instructions, connected knowledge, enabled tools, secrets, guardrails — each one directly affects how the agent answers real users.
A clear configuration produces an agent that behaves predictably in production. An incomplete or ambiguous one produces an agent that fails in ways that are hard to debug later, because nothing is technically broken — the agent is doing exactly what an unclear brief told it to. This guide is written to help you make each choice deliberately rather than by default.
New to agents? How an Agent Works walks through building one end to end. For the ideas behind the settings, see Core Concepts.
Maintained by Abhishek Paul
AI-assisted, human-approved
Last updated
Was this helpful?