Home›Agents›Oracle AI Agent Studio

AgentenCode evidence profileAutomation

✓ Editorially reviewedChecked: October 1, 2026

Agent profile · Automation

Oracle AI Agent Studio

Oracle AI Agent Studio is classified by AgentenCode as an enterprise agent builder from Oracle. It belongs to the Automation category. This English profile does not maintain a separate factual record: it renders the same underlying evidence, trust and history data as the German profile.

OracleAutomationOrganizations

View profile ↓Check sources ↓

Automationeditorial classification

Oracleprovider

14 primary sourcessource status

October 1, 2026last verification

AgentenTrust 2.0 · EU & governance evidence

Trust, privacy and control evidence for Oracle AI Agent Studio

Direct answer: AgentenCode currently documents 6 of 36 normalized trust controls for this profile. Missing fields remain Unknown and are never automatically interpreted as “no”.

EU AI ActEvidence context only. AgentenCode does not infer legal applicability or compliance from individual product controls.

GDPRPrivacy and security signals are documented field by field. Data residency alone is not a compliance or transfer assessment.

Privacy contextPrivacy & data1 of 8 documentedResidency, training, retention, DPA, subprocessors and processing scope.

Security contextSecurity & access3 of 10 documentedEncryption, SSO, SCIM, RBAC, roles and credential handling.

Human controlHuman control2 of 10 documentedApproval, oversight, permissions and stop or rollback controls.

TraceabilityAudit & traceability0 of 8 documentedAudit logs, APIs, SIEM, observability, tracing and activity history.

Important: these numbers show evidence coverage, not a product rating. 0 of 10 means that no field-level public evidence is stored for those ten controls in the current dataset. It does not mean the product lacks those capabilities.

Field-level evidence

Documented controls and values from primary sources.

Documented yesDocumented valueUnknown remains unknown

High confidence

API · Async

Yes — documented

External applications can invoke agent teams asynchronously.

Scope: external_agent_invocation · verified 2026-10-01 · Primary source ↗

High confidence

API · Auth · Oauth

Yes — documented

OAuth 2.0 bearer-token authentication is documented for external agent invocation.

Scope: external_agent_invocation · verified 2026-10-01 · Primary source ↗

High confidence

API · Rest

Yes — documented

External applications can invoke Fusion AI agent teams through documented REST endpoints.

Scope: external_agent_invocation · verified 2026-10-01 · Primary source ↗

High confidence

Composition · Tool

Document Tool

AI Agent Studio exposes Document as an explicit tool type that can be assigned to agents.

Scope: oracle_ai_agent_studio · verified 2026-10-03 · Primary source ↗

High confidence

Deployment · Import Export

Yes — documented

Cross-instance import/export is documented.

Scope: agent_teams_between_instances · verified 2026-10-01 · Primary source ↗

High confidence

Governance · Approval · Pre Action

Yes — documented

Document Tool can require a person to review and approve an action before the tool runs.

Scope: document_tool_actions · verified 2026-10-03 · Primary source ↗

High confidence

Governance · Custom roles

Yes — documented

Custom roles are supported.

Scope: fusion_security_console · verified 2026-10-01 · Primary source ↗

High confidence

Governance · Human approval

Yes — documented

Human approval steps can be added for oversight of agent actions.

Scope: agent_actions_and_workflows · verified 2026-10-01 · Primary source ↗

High confidence

Governance · Monitoring Access Control

Yes — documented

Monitoring records are access-controlled.

Scope: monitoring_and_evaluation · verified 2026-10-01 · Primary source ↗

High confidence

Governance · Observability

Yes — documented

AI Agent Studio includes run-level monitoring and metrics.

Scope: monitoring_and_evaluation · verified 2026-10-01 · Primary source ↗

High confidence

Governance · RBAC

Yes — documented

Role-based access is documented.

Scope: fusion_roles · verified 2026-10-01 · Primary source ↗

High confidence

Governance · Tracing

Yes — documented

Detailed per-session tracing is documented.

Scope: monitoring_and_evaluation · verified 2026-10-01 · Primary source ↗

High confidence

Hosting · Managed

Yes — documented

AI Agent Studio runs as a native capability of Oracle Fusion Cloud Applications on the Oracle AI Platform for Fusion Applications.

Scope: oracle_fusion_ai_platform_for_ai_agent_studio · verified 2026-10-01 · Primary source ↗

High confidence

Operations · Max Files Per Conversation

Oracle documents a maximum of five files uploaded per chat conversation.

Scope: chat_file_upload · verified 2026-10-03 · Primary source ↗

High confidence

Operations · Max Interactions Configurable

Yes — documented

Agent Settings expose a Maximum Interactions field controlling how many times an agent can interact with assigned topics and tools.

Scope: agent_configuration · verified 2026-10-03 · Primary source ↗

High confidence

Operations · Max Upload Mb Per Conversation

Oracle documents a combined 50 MB upload limit across files in one chat conversation.

Scope: chat_file_upload · verified 2026-10-03 · Primary source ↗

High confidence

Privacy · Data residency · Available

Yes — documented

The Fusion AI platform instance is region-local. This claim does not assert that generative-model processing always remains in the local OCI region.

Scope: fusion_ai_platform_instance_local_oci_region_at_rest · verified 2026-10-01 · Primary source ↗

High confidence

Protocols · A2A · Client

Yes — documented

Fusion Applications agents can call external A2A agents.

Scope: fusion_ai_agent_studio_26c · verified 2026-10-01 · Primary source ↗

Evidence-backed overview

What is Oracle AI Agent Studio?

Product-specific evidence for Oracle AI Agent Studio

This profile links 14 unique primary sources across the product profile, field-level evidence, trust controls and documented relations. The points below describe this product’s stored evidence rather than generic characteristics of Automatisierung.

Data Residency

Yes · Scope: fusion_ai_platform_instance_local_oci_region_at_rest · verified 2026-10-01.

Primary source ↗

Verschlüsselung at rest

Oracle Transparent Data Encryption (TDE) · Scope: oracle_fusion_applications_data_layer_used_by_ai_agent_studio · verified 2026-10-01.

Primary source ↗

Pre-Action Approval

Yes · Scope: document_tool_actions · verified 2026-10-03.

Primary source ↗

Custom Roles

Yes · Scope: fusion_security_console · verified 2026-10-01.

Primary source ↗

Human Approval

Yes · Scope: agent_actions_and_workflows · verified 2026-10-01.

Primary source ↗

governance · monitoring_access_control

Yes · Scope: monitoring_and_evaluation · verified 2026-10-01.

Primary source ↗

AgentenCode treats this page as a reference profile rather than a ranking. Product facts are separated from editorial classification, and the profile is tied to a specific verification date. If a capability is not backed by sufficiently precise public evidence, it remains unknown instead of being inferred from marketing language or from similar products.

1primary source

26field-level evidence claims

6documented trust controls

3history events

How to read the evidence

The field-level evidence layer records a value, a scope, a confidence level, a verification date and one or more primary sources. Scope matters: an enterprise-only security feature must not be generalized to every plan or deployment surface. The same rule applies to hosting, privacy, audit and protocol claims.

AgentenCode also keeps Unknown distinct from false. A missing claim means the public dataset does not currently contain sufficiently precise evidence for that field. A negative value is used only when a reliable primary source explicitly documents a restriction or non-availability.

Decision context

Provider and category

Oracle AI Agent Studio is documented under Automation and is associated with Oracle. Category labels help navigation but do not replace product-specific evidence.

Verification status

The public profile is marked editorially reviewed and was last checked on October 1, 2026.

Trust coverage

6 of 36 normalized trust controls currently have field-level public evidence. The remaining controls are not treated as negative findings.

Source-first use

For procurement, security or legal decisions, use the linked primary sources and verify the plan, region and configuration that apply to your organization.

Capabilities, strengths and deployment checks for Oracle AI Agent Studio

Oracle AI Agent Studio is classified as Enterprise Agent Builder from Oracle. The profile’s editorial layer is derived from the stored use cases, strengths and checks below; claims about security, privacy or governance remain separate and require field-level evidence.

ERP-Prozesse

This use case is part of the stored profile for Oracle AI Agent Studio. The related strength is “Tiefe Oracle-Fusion-Integration”. In a production evaluation, the practical boundary to verify is: Fusion-Berechtigungen prüfen.

HR

This use case is part of the stored profile for Oracle AI Agent Studio. The related strength is “Business-Kontext”. In a production evaluation, the practical boundary to verify is: kritische Finanz- oder HR-Aktionen mit Human-in-the-loop absichern.

Finance

This use case is part of the stored profile for Oracle AI Agent Studio. The related strength is “Multi-Agent- und Tool-Funktionen”. In a production evaluation, the practical boundary to verify is: MCP/A2A-Verbindungen kontrollieren.

Supply Chain

This use case is part of the stored profile for Oracle AI Agent Studio. The related strength is “Governance im Enterprise-Umfeld”. In a production evaluation, the practical boundary to verify is: Fusion-Berechtigungen prüfen.

What to verify before adoption

Fusion-Berechtigungen prüfen. Treat undocumented controls as Unknown and verify the exact plan, region and deployment scope.
kritische Finanz- oder HR-Aktionen mit Human-in-the-loop absichern. Treat undocumented controls as Unknown and verify the exact plan, region and deployment scope.
MCP/A2A-Verbindungen kontrollieren. Treat undocumented controls as Unknown and verify the exact plan, region and deployment scope.

Editorial boundary: The use-case and strength descriptions are product-specific editorial context based on the stored profile. Trust, privacy and governance statements are only presented as facts when field-level primary-source evidence exists.

Verified history

The public history layer records only confirmed profile changes and verification events. Monitoring signals are not published as product facts until they have been reviewed.

October 1, 2026 · Source Maintenance
September 30, 2026 · Verification Update
September 28, 2026 · Schema Upgrade

Official sources

This profile links 14 unique primary sources across the product profile, field-level evidence, trust layer and documented relations. Provider documentation remains authoritative when the product changes between verification cycles.

Frequently asked questions

What is Oracle AI Agent Studio?

Oracle AI Agent Studio is listed by AgentenCode as an automation agent or agentic product from Oracle.

How much trust evidence is documented for Oracle AI Agent Studio?

The current trust layer documents 6 of 36 normalized controls. Missing controls remain unknown rather than being treated as false.

When was this profile last checked?

The current profile verification date is October 1, 2026. The linked primary sources remain authoritative if the product changes between checks.

Method note: AgentenCode does not certify GDPR or EU AI Act compliance. It documents evidence that can support a separate legal, security or procurement assessment.