Aleph Alpha API

AI servicealeph-alpha-api

Luminous and Pharia model API from Aleph Alpha, now shipped inside PhariaAI installations.

Provider: default
Kind: AI service
Category: Compute
Official docs: https://docs.aleph-alpha.com/phariaai-dev-guide/latest/pharia-openapi/index.html
Also known as: PhariaAI, PhariaInference API, Luminous

Properties · 2 set by this component

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

Other AI service products · 125

and 85 more → AI service page

Source

1# yaml-language-server: $schema=../../schema/component.schema.json
2# Aleph Alpha API: Luminous and Pharia model endpoints from the German sovereign-AI vendor, token-authenticated.
3# Retired November 2024: the public hosted API was discontinued on 30 November 2024; the API now ships inside a
4# customer-operated PhariaAI installation ("Aleph Alpha API reference"). Cohere agreed to acquire Aleph Alpha in April 2026.
5schemaVersion: "1"
6type: "component"
7id: "aleph-alpha-api"
8kind: "ai-service"
9provider: "default"
10docs: "https://docs.aleph-alpha.com/phariaai-dev-guide/latest/pharia-openapi/index.html"
11aliases: ["PhariaAI", "PhariaInference API", "Luminous"]
12defaults:
13  auth: "api-key"
14  modality: "multimodal"
15properties:
16  deployment:
17    type: "enum"
18    values: ["public-api", "pharia-on-premise", "pharia-hosted"]
19    default: "pharia-on-premise"
20  selfHosted:
21    type: "boolean"
22    default: true

The same page as markdown, for an agent: /catalogue/components/aleph-alpha-api.md