Dialogflow ES

gcp AI servicegoogle-dialogflow-es

Intent-and-context virtual agent, one per project per region.

Provider: gcp
Kind: AI service
Category: Compute
Official docs: https://docs.cloud.google.com/dialogflow/quotas

Properties · 5 set by this component

property	type	values	required	kind default	this component
audioRequestsPerMinute · component property	integer	—	no	100	inherited
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
edition · component property	enum	trial \| essentials \| plus	no	trial	inherited
keyStore	boolean	—	no	false	inherited
managed	boolean	—	no	false	▸ true
maxEntityTypes · component property	integer	—	no	250	inherited
maxInputCharacters · component property	integer	—	no	256	inherited
maxIntents · component property	integer	—	no	2000	inherited
modality	enum	text \| vision \| speech \| multimodal \| structured \| image \| video \| audio \| embedding \| rerank	no	—	▸ multimodal
publicEndpoint	boolean	—	no	—	▸ true
quotaUnitsPerMinute	integer	—	no	—	▸ 180
rateLimitRpm · advanced	integer	—	no	—	inherited
rateLimitTpm · advanced	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: "dialogflow-es", component: "google-dialogflow-es" }

Other AI service products · 125

and 85 more → AI service page

Source

1# yaml-language-server: $schema=../../schema/component.schema.json
2# Dialogflow ES agent: the intent-and-context virtual agent, one agent per project per
3# region. "Quotas and limits": Trial Edition allows 180 text and 100 audio detect-intent
4# requests per minute, Essentials 600 and 300; 2,000 intents and 250 entity types per
5# agent; 60 seconds of audio and 256 characters of input text per request.
6schemaVersion: "1"
7type: "component"
8id: "google-dialogflow-es"
9kind: "ai-service"
10provider: "gcp"
11docs: "https://docs.cloud.google.com/dialogflow/quotas"
12defaults:
13  auth: "iam"
14  modality: "multimodal"
15  publicEndpoint: true
16  quotaUnitsPerMinute: 180
17  managed: true
18properties:
19  edition:
20    type: "enum"
21    values: ["trial", "essentials", "plus"]
22    default: "trial"
23  audioRequestsPerMinute:
24    type: "integer"
25    default: 100
26  maxIntents:
27    type: "integer"
28    default: 2000
29  maxEntityTypes:
30    type: "integer"
31    default: 250
32  maxInputCharacters:
33    type: "integer"
34    default: 256

The same page as markdown, for an agent: /catalogue/components/google-dialogflow-es.md