Oracle AI Agent Studio Components
The Oracle AI Agent Studio components are the reusable building blocks you assemble to create a working Fusion AI agent: agents, agent teams, topics, instructions and natural-language prompts, tools, knowledge sources, and prebuilt templates. Each is configured inside AI Agent Studio and combines with the others to define what an agent knows, what it can decide, and what it is allowed to do. This page is the catalog of those blocks and links out to the deep page for each.
Last reviewed: 19 July 2026
AI Agent Studio has been generally available since Oracle release 25C. This page catalogs the components and how they fit; for the product overview, enablement, and roles, see the Oracle AI Agent Studio overview.
What Counts as a Component in AI Agent Studio
In Oracle AI Agent Studio, a component is any configurable element you define once and reuse when building an agent. Rather than writing code, you assemble these elements declaratively: you describe the agent's purpose in natural language, scope it to one or more topics, give it tools to take action, point it at knowledge sources for grounding, and — where the work spans multiple specialist agents — coordinate them as a team. Every component is a distinct object in Studio, which is what makes agents auditable and testable: you can inspect each block on its own before you trust the whole.
Understanding the components is the prerequisite for governing and testing Oracle's AI. An agent's behaviour is the sum of its parts — a loose instruction, an over-broad tool, or a stale knowledge source each changes what the agent does in production.
Scope note. This page is the catalog of building blocks and where each is configured. It intentionally stays shallow on any single block to avoid overlapping the deep pages. For the broad product overview — what AI Agent Studio is, how it is enabled, and the roles required — see the AI Agent Studio parent page. Each component below links out to its own dedicated deep page, which owns that detail.
The Building Blocks, One by One
Each block below gets a short orientation and a link to its deep page. All are configured inside AI Agent Studio and are generally available from release 25C unless a specific enhancement is noted with its own release.
Agents
An agent is a single AI worker configured to handle a defined job — for example, a Payables invoice-handling agent capability or an HCM candidate-screening agent capability. You define its purpose, the topics it covers, the instructions it follows, the tools it may call, and the knowledge it can draw on. A single agent is the smallest unit you can deploy into a Fusion workflow. The end-to-end how-to for creating one lives on the build an Oracle AI agent walkthrough.
Agent teams
An agent team is a group of specialist agents orchestrated to work on a shared objective, with a coordinating agent routing work between members. Oracle supports multi-agent orchestration with checkpoints and approvals, so a team can pause for a human decision before continuing. Teams are how larger, multi-step processes are composed from focused agents rather than one over-loaded agent. The orchestration logic and design patterns are covered on the Oracle AI agent teams page.
Topics
A topic is a scoped subject area the agent is responsible for — it defines the boundary of what the agent will engage with and helps route a request to the right handling. Topics keep an agent focused and make its behaviour predictable, which matters for both accuracy and testing. How topics are structured, scoped, and validated is detailed on the Oracle AI agent topics page.
Instructions and natural-language prompts
Instructions are the natural-language prompts that tell the agent how to behave — its tone, its rules, the steps it should follow, and the limits it must respect. Because behaviour is expressed in language rather than code, small wording changes can meaningfully shift outcomes, which is exactly why prompts need version control and regression testing. Prompt design, structure, and testing considerations are on the agent prompts and instructions page.
Tools
Tools are the actions an agent can take beyond conversation — calling an external REST service, invoking an MCP-compliant server, sending email, using a connector, or reading a document. External REST tools include a Require Human Approval option so a sensitive action pauses for sign-off before it executes. MCP tool support and REST-tool enhancements arrived in release 26A; email and document tools are part of the 25C baseline. The full catalog of tool types and how they are configured is on the Oracle AI agent tools page.
Knowledge sources
Knowledge sources are documents you upload so the agent can retrieve grounded answers through semantic search rather than relying only on the underlying model's general knowledge. They are how you give an agent your policies, procedures, and reference material. Keeping these current is a governance task in itself — a stale document produces confidently wrong answers. How knowledge sources are added, indexed, and validated is covered on the Oracle AI agent knowledge sources page.
Prebuilt templates
Templates are Oracle-provided starting points — the readiness material describes more than 50 prebuilt Fusion agent templates — that come pre-wired with sensible topics, instructions, and tools for common processes. A template accelerates the first build, but it is a starting point, not a finished configuration: you still tailor its instructions, scope its tools, and test it against your own data. Templates are browsed and instantiated from within AI Agent Studio, then customised through the build process.
Oracle AI Agent Studio Components at a Glance
A quick-reference map of every component: what it is, where it is configured, and the deep page that owns the detail. All components are configured inside AI Agent Studio (generally available from release 25C).
| Component | What it is | Where it's configured | Deep-dive link |
|---|---|---|---|
| Agent | A single AI worker scoped to one job | AI Agent Studio · agent definition | Build an Oracle AI agent |
| Agent team | Coordinated specialist agents on one objective, with checkpoints/approvals | AI Agent Studio · team orchestration | Oracle AI agent teams |
| Topic | A scoped subject area that bounds what the agent handles | AI Agent Studio · topics | Oracle AI agent topics |
| Instructions / prompts | Natural-language rules that shape the agent's behaviour | AI Agent Studio · instructions | Agent prompts & instructions |
| Tools | Actions the agent can take — REST, MCP, connectors, email, documents | AI Agent Studio · tools | Oracle AI agent tools |
| Knowledge sources | Uploaded documents for grounded semantic-search answers | AI Agent Studio · knowledge | Oracle AI agent knowledge sources |
| Templates | 50+ prebuilt Fusion agent starting points to customise | AI Agent Studio · template gallery | AI Agent Studio overview |
How the Components Assemble Into a Working Agent
The components are not a flat checklist — they layer. A useful way to picture an agent is as a set of concentric decisions: what it is for, what it will engage with, how it should reason, what it can act on, and what it knows. Where one agent is not enough, a team wires several together.
Assembly sequence
- Template first (optional): instantiate a prebuilt Fusion template to inherit a working baseline, then customise every block.
- Agent and purpose: the agent object holds the definition that binds the other components together.
- Topics scope it: topics set the boundary so the agent engages only with what it should.
- Instructions govern reasoning: natural-language prompts encode the rules, steps, and limits.
- Tools grant action: attach only the tools the job needs; use Require Human Approval on sensitive external actions.
- Knowledge grounds answers: upload the documents the agent should cite through semantic search.
- Teams for multi-step work: coordinate specialist agents with checkpoints and human approvals where the process spans several steps.
- Validate and deploy: Studio's debugging and validation tools let you exercise the agent before it is deployed into a Fusion workflow.
For the step-by-step version of this sequence with screens and worked examples, follow the build an Oracle AI agent guide.
Testing, Configuration and Security Notes
Because each component changes behaviour independently, each is also a place where a defect or a control gap can be introduced. A few practical notes for Oracle Fusion customers who must govern and test these agents:
- Instructions are code you cannot compile. A prompt edit has no type-checker to catch it. Version prompts, and regression-test the agent's outputs after any instruction change so wording drift is caught before production.
- Tools are the security perimeter. A tool is what lets an agent act on the outside world. Grant the minimum set, prefer the Require Human Approval option on external REST actions that write or transact, and confirm the agent operates within existing Fusion role-based permissions, policies, and approvals rather than around them.
- Knowledge sources decay. Retrieval only helps if the underlying documents are current. Treat re-indexing and document review as a recurring governance task, and test that the agent cites the right source version.
- Teams add orchestration risk. Multi-agent flows introduce routing, checkpoints, and hand-offs that each need their own test cases — including the human-approval gates firing when they should.
- Quarterly updates can shift behaviour. New tool types and platform enhancements arrive each release (MCP tools and REST enhancements in 26A, A2A interoperability announced for 26C). Re-validate agents after an update the same way you would any other Fusion change.
How SyntraFlow fits. SyntraFlow's Oracle Fusion testing platform can be configured to help organisations validate agent-backed processes as part of their broader ERP regression coverage — for example, exercising the Fusion transactions an agent triggers and checking outcomes after a quarterly update. This is complementary to Oracle's own in-Studio validation, not a replacement for it, and the specifics depend on your configuration. See the Oracle ERP testing tool for how that coverage is approached. SyntraFlow's testing engine is distinct from Oracle's AI agents — it is used to test Oracle, including where Oracle uses AI.
Official Oracle References
The component descriptions above are drawn from Oracle's own documentation. Verify current availability and behaviour against these sources. Last reviewed: 19 July 2026.
- Oracle Fusion AI — product page
- AI Agent Studio key capabilities (agents, teams, topics, tools, instructions, knowledge sources, templates)
- 25C readiness — AI Agent Studio general availability
- Add an external REST tool (Require Human Approval)
- Add an MCP tool (26A)
Availability labels used above: AI Agent Studio and its core components are generally available (release 25C); MCP tools and REST-tool enhancements are generally available (release 26A); Agent2Agent (A2A) interoperability is announced for release 26C. Confirm current availability with Oracle before relying on any capability.
Frequently Asked Questions
What are the components of Oracle AI Agent Studio?
▼
The core building blocks are agents, agent teams, topics, instructions and natural-language prompts, tools, knowledge sources, and prebuilt templates. Each is a configurable object inside AI Agent Studio, and you combine them to define what an agent knows, what it will engage with, how it reasons, and what actions it can take. AI Agent Studio has been generally available since release 25C.
How is this page different from the AI Agent Studio overview?
▼
This page is the catalog of building blocks — it names each component, says where it is configured, and links out to the deep page that owns the detail. The broad product overview — what AI Agent Studio is, how it is enabled, and the roles it needs — lives on the AI Agent Studio parent page. Use this page to understand the pieces; use the overview to understand the product.
What is the difference between a topic and an instruction?
▼
A topic sets the boundary of what the agent will engage with — the subject areas it is responsible for. An instruction is the natural-language guidance for how the agent behaves within that boundary: its rules, steps, tone, and limits. Topics scope; instructions govern reasoning. The topics and prompts and instructions pages cover each in depth.
What kinds of tools can an agent use?
▼
Tools give an agent the ability to act: external REST tools to call third-party APIs (with an optional Require Human Approval gate), MCP tools to connect to MCP-compliant servers, connector tools, email tools, and document tools. External REST and MCP capabilities were enhanced or added in release 26A; email and document tools are part of the 25C baseline. The full catalog is on the agent tools page.
When do I need an agent team instead of a single agent?
▼
Use a single agent for a focused job with one clear purpose. Use an agent team when the work spans several specialised steps that are cleaner to handle as separate agents coordinated together — Oracle supports multi-agent orchestration with checkpoints and human approvals. Composing agents into a team is covered on the agent teams page.
Are the prebuilt templates ready to use as-is?
▼
Oracle's readiness material describes more than 50 prebuilt Fusion agent templates, and they are a strong starting point — but they are a baseline, not a finished configuration. You should tailor the instructions, scope the tools, point them at your own knowledge sources, and test against your data before deploying. The customisation flow is on the build an agent page.
How do knowledge sources differ from tools?
▼
A knowledge source is passive reference material — documents you upload so the agent can retrieve grounded answers through semantic search. A tool is active — it lets the agent take an action, such as calling an API or sending email. Knowledge shapes what the agent knows; tools shape what it can do. The knowledge sources page details how documents are added and indexed.
How should I test agents built from these components?
▼
Test each component's contribution as well as the whole: regression-test prompt changes, confirm tools stay within role-based permissions and that human-approval gates fire, verify knowledge sources are current, and re-validate after each quarterly update. AI Agent Studio provides in-product debugging and validation; SyntraFlow can be configured to help organisations assess the downstream Fusion transactions an agent affects as part of broader regression coverage. See the Oracle ERP testing tool.
Understand and Govern Your Oracle AI Agents
Get a clear picture of the AI Agent Studio components in your Fusion environment, the risks each introduces, and how to test agent-backed processes through quarterly updates. SyntraFlow can help you assess readiness and coverage.