OCI Document Understanding

ociAI serviceoci-document-understanding

Extracts text, key values, tables and document classes from documents and PDFs.

Provider
oci
Category
Compute
Properties · 5 set by this component
propertytypevaluesrequiredkind defaultthis component
authenumapi-key | oauth | iam | noneno—▸ iam
contentFilteringboolean—no—inherited
customerManagedKeysboolean—no—inherited
dataResidency · advancedenumus | eu | asia | globalno—inherited
dataRetentionDaysinteger—no—inherited
keyStoreboolean—nofalseinherited
managedboolean—nofalse▸ true
maxAsyncPagesPerDocument · component propertyinteger—no2000inherited
maxDocumentsPerJob · component propertyinteger—no2000inherited
maxSyncFileMb · component propertyinteger—no8inherited
maxSyncPages · component propertyinteger—no5inherited
modalityenumtext | vision | speech | multimodal | structured | image | video | audio | embedding | rerankno—▸ structured
modelType · component propertyenumpretrained | customnopretrainedinherited
processing · component propertyenumsync | asyncnosyncinherited
publicEndpointboolean—no—▸ true
quotaUnitsPerMinuteinteger—no—▸ 300
rateLimitRpm · advancedinteger—no—inherited
rateLimitTpm · advancedinteger—no—inherited
viaGatewayboolean—nofalseinherited
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-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-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: "document-understanding", component: "oci-document-understanding" }
Other AI service products · 125
Content Moderationalibaba-content-moderationalibabacloudai-serviceFraud Detectionalibaba-fraud-detectionalibabacloudai-serviceID Verificationalibaba-id-verificationalibabacloudai-serviceIntelligent Robotalibaba-intelligent-robotalibabacloudai-serviceModel Studioalibaba-model-studioalibabacloudai-serviceSmart Conversation Analysisalibaba-smart-conversation-analysisalibabacloudai-serviceAmazon Bedrockaws-bedrockawsai-serviceAmazon Bedrock AgentCoreaws-bedrock-agentcoreawsai-serviceAmazon Bedrock Data Automationaws-bedrock-data-automationawsai-serviceAmazon Bedrock Guardrailsaws-bedrock-guardrailsawsai-serviceAmazon Comprehendaws-comprehendawsai-serviceAmazon Comprehend Medicalaws-comprehend-medicalawsai-serviceAWS Elemental Inferenceaws-elemental-inferenceawsai-serviceAmazon Forecastaws-forecastawsai-serviceAmazon Fraud Detectoraws-fraud-detectorawsai-serviceAWS HealthScribeaws-healthscribeawsai-serviceAmazon Lex botaws-lexawsai-serviceAmazon Lookout for Equipmentaws-lookout-for-equipmentawsai-serviceAmazon Lookout for Metricsaws-lookout-for-metricsawsai-serviceAmazon Lookout for Visionaws-lookout-for-visionawsai-serviceAmazon Personalizeaws-personalizeawsai-serviceAmazon Pollyaws-pollyawsai-serviceAmazon Q Businessaws-q-businessawsai-serviceAmazon Rekognitionaws-rekognitionawsai-serviceAmazon Textractaws-textractawsai-serviceAmazon Transcribeaws-transcribeawsai-serviceAmazon Translateaws-translateawsai-serviceContent Safetyazure-ai-content-safetyazureai-serviceAzure AI Custom Visionazure-ai-custom-visionazureai-serviceAzure AI Faceazure-ai-faceazureai-serviceAzure Languageazure-ai-languageazureai-serviceAzure Speechazure-ai-speechazureai-serviceAzure Translatorazure-ai-translatorazureai-serviceAzure Visionazure-ai-visionazureai-serviceAzure Content Understandingazure-content-understandingazureai-serviceMicrosoft Discoveryazure-discoveryazureai-serviceAzure Document Intelligenceazure-document-intelligenceazureai-serviceFoundry Agent Serviceazure-foundry-agent-serviceazureai-serviceFoundry Modelsazure-foundry-modelsazureai-serviceAzure AI Immersive Readerazure-immersive-readerazureai-service
and 85 more → AI service page
Source
# yaml-language-server: $schema=../../schema/component.schema.json
# Oracle OCI Document Understanding: managed endpoint that turns documents into structured
# output (OCR, key-value extraction, table extraction, document classification).
# "Document Understanding Limits": 300 asynchronous transactions per minute per tenancy,
# 8 MB and 5 pages per synchronous request, 500 MB and 2,000 pages per document read from
# Object Storage, 2,000 documents per batch job.
schemaVersion: "1"
type: "component"
id: "oci-document-understanding"
kind: "ai-service"
provider: "oci"
docs: "https://docs.oracle.com/en-us/iaas/Content/document-understanding/using/limits.htm"
defaults:
  auth: "iam"
  modality: "structured"
  publicEndpoint: true
  quotaUnitsPerMinute: 300
  managed: true
properties:
  processing:
    type: "enum"
    values: ["sync", "async"]
    default: "sync"
  modelType:
    type: "enum"
    values: ["pretrained", "custom"]
    default: "pretrained"
  maxSyncPages:
    type: "integer"
    default: 5
  maxSyncFileMb:
    type: "integer"
    default: 8
  maxAsyncPagesPerDocument:
    type: "integer"
    default: 2000
  maxDocumentsPerJob:
    type: "integer"
    default: 2000

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