Cloud Translation API

gcp AI servicegoogle-cloud-translation

Machine translation of text and documents, with optional glossaries and custom models.

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

Properties · 5 set by this component

property	type	values	required	kind default	this component
auth	enum	api-key \| oauth \| iam \| none	no	—	▸ iam
batchTranslation · component property	boolean	—	no	false	inherited
charactersPerMinute · component property	integer	—	no	6000000	inherited
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	basic \| advanced	no	advanced	inherited
glossary · component property	boolean	—	no	false	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
model · component property	enum	general \| custom-automl \| adaptive	no	general	inherited
publicEndpoint	boolean	—	no	—	▸ true
quotaUnitsPerMinute	integer	—	no	—	▸ 6000
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: "cloud-translation", component: "google-cloud-translation" }

Other AI service products · 125

and 85 more → AI service page

Source

1# yaml-language-server: $schema=../../schema/component.schema.json
2# Google Cloud Translation API: metered machine translation. "Quotas and limits":
3# 6,000 v3 requests per minute, 6 million characters per minute on the general model,
4# 100,000 characters per minute on custom (AutoML) models, 2,400 document pages per minute.
5schemaVersion: "1"
6type: "component"
7id: "google-cloud-translation"
8kind: "ai-service"
9provider: "gcp"
10docs: "https://docs.cloud.google.com/translate/quotas"
11defaults:
12  auth: "iam"
13  modality: "text"
14  publicEndpoint: true
15  quotaUnitsPerMinute: 6000
16  managed: true
17properties:
18  edition:
19    type: "enum"
20    values: ["basic", "advanced"]
21    default: "advanced"
22  model:
23    type: "enum"
24    values: ["general", "custom-automl", "adaptive"]
25    default: "general"
26  charactersPerMinute:
27    type: "integer"
28    default: 6000000
29  glossary:
30    type: "boolean"
31    default: false
32  batchTranslation:
33    type: "boolean"
34    default: false

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