Language Overview

Language is serverless and multi-tenant service that is accessible using REST API calls. It provides pretrained models that are frequently retrained and monitored to provide you with the best results.

You can automate sophisticated text analysis at scale without any machine learning expertise.

The Language service contains these pretrained language processing capabilities:
Language Detection
Detects languages based on the given text, and includes a confidence score.
Text Classification

Identifies the document category and subcategory that the text belongs to.

Named Entity Recognition

Identifies common entities, people, places, locations, email, and so on.

Key Phrase Extraction

Extracts an important set of phrases from a block of text.

Sentiment Analysis

Identifies aspects from the given text and classifies each into positive, negative, or neutral polarity.

Ways to Access Language

You access Language using the Console, REST API, SDKs, or CLI.

Use any of the following options, based on your preference and its suitability for the task you want to complete:

  • The OCI Console is an easy-to-use, browser-based interface. To access the Console, you must use a supported browser.
  • The REST APIs provide the most functionality, but require programming expertise. API reference and endpoints provide endpoint details and links to the available API reference documents including the Artificial Intelligence Services REST API.
  • OCI provides SDKs that interact with Language without the need to create a framework.
  • The CLI provides both quick access and full functionality without the need for programming.

Regions and Availability Domains

OCI services are hosted in regions and availability domains. A region  is a localized geographic area, and an availability domain  is one or more data centers located in that region.

Language is hosted in these regions:

  • Australia East (Sydney)

  • Australia Southeast (Melbourne)

  • Brazil East (Sao Paulo)

  • Canada Southeast (Montreal)

  • Canada Southeast (Toronto)

  • Chile (Santiago)

  • Dedicated Region Cloud@Customer (Chiyoda)

  • Germany Central (Frankfurt)

  • India South (Hyderabad)

  • India West (Mumbai)

  • Japan Central (Osaka)

  • Japan East (Tokyo)

  • Netherlands Northwest (Amsterdam)

  • Saudi Arabia West (Jeddah)

  • South Africa Central (Johannesburg)

  • South Korea Central (Seoul)

  • South Korea North (Chuncheon)

  • Sweden Central (Stockholm)

  • Switzerland North (Zurich)

  • UAE East (Dubai)

  • UK South (London)

  • UK West (Newport)

  • US East (Ashburn)

  • US West (Phoenix)

  • US West (San Jose)

About Language Policies

Learn about the resource policies including API permissions.

To control who has access to Language and the type of access for each group of users, you must create policies. By default, only the users in the Administrators group have access to all Language resources. For everyone else who's using the service, you must create new policies that assign them proper rights to Language resources. For a complete list of OCI policies, see Policy Reference.

Resource Types

Language offers both aggregate and individual resource-types for writing policies. You can use aggregate resource types to write fewer policies. For example, instead of allowing a group to manage all of the individual resource types, you can have a policy that allows the group to manage the aggregate resource type, ai-service-language-family.

Individual Resource Types




Aggregate Resource Type
Example Policies
allow group <language-group> to use <ai-service-language-family> in tenancy

Permissions Required for Each API Operation

You can use the individual resource types with API calls to interact with the service.

The following table lists the API operations for the Language service in a logical order, grouped by resource type, and the permissions required for resource types:

API Operation Permissions