Intelligent Robot

alibabacloud AI servicealibaba-intelligent-robot

NLP dialogue platform that answers from an ontology-based knowledge base and drives multi-round conversations across chat clients.

Provider: alibabacloud
Kind: AI service
Category: Compute
Official docs: https://www.alibabacloud.com/product/bot

Properties · 2 set by this component

property	type	values	required	kind default	this component
auth	enum	api-key \| oauth \| iam \| none	no	—	inherited
contentFiltering	boolean	—	no	—	inherited
customerManagedKeys	boolean	—	no	—	inherited
dataResidency · advanced	enum	us \| eu \| asia \| global	no	—	inherited
dataRetentionDays	integer	—	no	—	inherited
keyStore	boolean	—	no	false	inherited
knowledgeBase · component property	boolean	—	no	true	inherited
managed	boolean	—	no	false	▸ true
modality	enum	text \| vision \| speech \| multimodal \| structured \| image \| video \| audio \| embedding \| rerank	no	—	▸ text
multiTurnDialogue · component property	boolean	—	no	true	inherited
publicEndpoint	boolean	—	no	—	inherited
quotaUnitsPerMinute	integer	—	no	—	inherited
rateLimitRpm · advanced	integer	—	no	—	inherited
rateLimitTpm · advanced	integer	—	no	—	inherited
thirdPartyApiCallout · component property	boolean	—	no	false	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: "intelligent-robot", component: "alibaba-intelligent-robot" }

Other AI service products · 125

and 85 more → AI service page

Source

1# yaml-language-server: $schema=../../schema/component.schema.json
2# Intelligent Robot (Chatbot): "a dialogue platform that enables smart dialogue through various
3# dialogue-enabling clients, such as websites, mobile apps, and robots", powered by natural language
4# processing ("Intelligent Robot: Smart Conversation Platform Based on NLP"). That page states it recognises
5# and processes Chinese and English text, ships an ontology-based knowledge base with preset domain packages,
6# and that the Bot Framework configures multi-round dialogue and integrates third-party APIs.
7schemaVersion: "1"
8type: "component"
9id: "alibaba-intelligent-robot"
10kind: "ai-service"
11provider: "alibabacloud"
12docs: "https://www.alibabacloud.com/product/bot"
13defaults:
14  managed: true
15  modality: "text"
16properties:
17  knowledgeBase:
18    type: "boolean"
19    default: true
20  multiTurnDialogue:
21    type: "boolean"
22    default: true
23  thirdPartyApiCallout:
24    type: "boolean"
25    default: false

The same page as markdown, for an agent: /catalogue/components/alibaba-intelligent-robot.md