Oracle Digital Assistant

oci AI serviceoci-digital-assistant

Managed conversational AI instance fronting skills across chat channels.

Provider: oci
Kind: AI service
Category: Compute
Official docs: https://docs.oracle.com/en-us/iaas/digital-assistant/doc/order-service-and-provision-instance.html
Also known as: ODA

Properties · 4 set by this component

property	type	values	required	kind default	this component
auth	enum	api-key \| oauth \| iam \| none	no	—	▸ iam
contentFiltering	boolean	—	no	—	inherited
customerManagedKeys	boolean	—	no	—	inherited
dataResidency · advanced	enum	us \| eu \| asia \| global	no	—	inherited
dataRetentionDays	integer	—	no	—	inherited
insightsStorageGb · component property	integer	—	no	—	inherited
instanceShape · component property	enum	development \| production	no	—	inherited
keyStore	boolean	—	no	false	inherited
managed	boolean	—	no	false	▸ true
modality	enum	text \| vision \| speech \| multimodal \| structured \| image \| video \| audio \| embedding \| rerank	no	—	▸ text
privateEndpoint · component property	boolean	—	no	false	inherited
publicEndpoint	boolean	—	no	—	▸ true
quotaUnitsPerMinute	integer	—	no	—	inherited
rateLimitRpm · advanced	integer	—	no	—	inherited
rateLimitTpm · advanced	integer	—	no	—	inherited
requestRateLimitPerMinute · component property	integer	—	no	—	inherited
viaGateway	boolean	—	no	false	inherited

Rules that apply · 2

Every rule whose selector covers this component's kind or its category. Whether a rule fires depends on the design: its properties, its edges and its groups.

AI API key not managedwarning

ai-api-key-unmanaged

This AI vendor is reached with an API key, and nothing in the design holds or rotates that key. It ends up in environment files or code, every caller shares it, and a single leak runs up the vendor bill until someone notices. Put the key in a key-management component, or say it is held there with keyStore.

— all of these hold:
— the node's `auth` is "api-key"
— the node's `keyStore` is false
— the node has at least one incoming edge from an app-server, worker or client
— this does not hold:
— the design contains a node of kind key-management

Stateful node without zone redundancyerror

stateful-node-without-zone-redundancy

A stateful compute node pinned to exactly one availability zone disappears with that zone, and its state goes with it. Nodes inside a cell are exempt, because there the cell is deliberately single-zone and redundancy comes from the other cells.

— all of these hold:
— the node's `stateless` is false
— the node sits inside exactly 1 availability-zone group
— this does not hold:
— the node sits inside at least one cell group

Use it in a design

nodes:
  - { id: "digital-assistant", component: "oci-digital-assistant" }

Other AI service products · 125

and 85 more → AI service page

Source

1# yaml-language-server: $schema=../../schema/component.schema.json
2# Oracle Digital Assistant: an Oracle-managed, region-bound conversational AI instance that
3# fronts skills over channels (Web, Slack, Microsoft Teams, Twilio, webhook).
4# "Order the Service and Provision an Instance": the shape sets the rate limit and insights
5# storage — Development 50 requests per minute and 40 GB, Production 500 and 100 GB; over the
6# limit the instance answers HTTP 429. No shape is documented as the default, so none is set.
7schemaVersion: "1"
8type: "component"
9id: "oci-digital-assistant"
10kind: "ai-service"
11provider: "oci"
12docs: "https://docs.oracle.com/en-us/iaas/digital-assistant/doc/order-service-and-provision-instance.html"
13aliases: ["ODA"]
14defaults:
15  auth: "iam"
16  modality: "text"
17  publicEndpoint: true
18  managed: true
19properties:
20  instanceShape:
21    type: "enum"
22    values: ["development", "production"]
23  requestRateLimitPerMinute:
24    type: "integer"
25  insightsStorageGb:
26    type: "integer"
27  privateEndpoint:
28    type: "boolean"
29    default: false

The same page as markdown, for an agent: /catalogue/components/oci-digital-assistant.md