Generic AI service
Vendor-neutral AI service. Use when the real product is not in the catalogue; every rule for this kind still applies.
- Provider
- default
- Kind
- AI service
- Category
- Compute
- Official docs
- not recorded
- Generic?
- Vendor-neutral: the kind itself
| property | type | values | required | default |
|---|---|---|---|---|
| auth | enum | api-key | oauth | iam | none | no | — |
| contentFiltering | boolean | — | no | — |
| customerManagedKeys | boolean | — | no | — |
| dataResidency | enum | us | eu | asia | global | no | — |
| dataRetentionDays | integer | — | no | — |
| keyStore | boolean | — | no | false |
| managed | boolean | — | no | false |
| modality | enum | text | vision | speech | multimodal | structured | image | video | audio | embedding | rerank | no | — |
| publicEndpoint | boolean | — | no | — |
| quotaUnitsPerMinute | integer | — | no | — |
| rateLimitRpm | integer | — | no | — |
| rateLimitTpm | integer | — | no | — |
| viaGateway | boolean | — | no | false |
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.
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
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
nodes:
- { id: "ai-service", component: "ai-service" }# yaml-language-server: $schema=../../schema/component.schema.json # The vendor-neutral AI service: the kind itself, with no product behind it. It sets no # defaults and adds no properties, so every required kind property stays required on the node. schemaVersion: "1" type: "component" id: "ai-service" kind: "ai-service" provider: "default"