Reka API

Hosted multimodal models for chat over text, image, video and audio, plus video search and clipping.

Provider: default
Kind: AI service
Category: Compute
Official docs: https://docs.reka.ai/vision/rate-limits
Also known as: Reka Chat, Reka Vision, Reka Clip

Properties · 4 set by this component

property	type	values	required	kind default	this component
api · component property	enum	chat \| vision	no	chat	inherited
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
keyStore	boolean	—	no	false	inherited
managed	boolean	—	no	false	▸ true
modality	enum	text \| vision \| speech \| multimodal \| structured \| image \| video \| audio \| embedding \| rerank	no	—	▸ multimodal
prepaidCredits · component property	boolean	—	no	true	inherited
publicEndpoint	boolean	—	no	—	▸ true
quotaUnitsPerMinute	integer	—	no	—	inherited
rateLimitRpm · advanced	integer	—	no	—	inherited
rateLimitTpm · advanced	integer	—	no	—	inherited
viaGateway	boolean	—	no	false	inherited
videoUploadsPerDay · component property	integer	—	no	50	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: "reka-api", component: "reka-api" }

Other AI service products · 125

and 85 more → AI service page

Source

1# yaml-language-server: $schema=../../schema/component.schema.json
2# Reka API: hosted multimodal chat models (text, image, video, audio input) plus the Reka Vision video API.
3# Per "Reka API Documentation" requests authenticate with an X-Api-Key header; per "FAQs" credits are prepaid and
4# a zero balance returns P001; per "Rate Limits", Vision endpoints allow 10-100 requests per API key per 24 hours.
5schemaVersion: "1"
6type: "component"
7id: "reka-api"
8kind: "ai-service"
9provider: "default"
10docs: "https://docs.reka.ai/vision/rate-limits"
11aliases: ["Reka Chat", "Reka Vision", "Reka Clip"]
12defaults:
13  auth: "api-key"
14  managed: true
15  modality: "multimodal"
16  publicEndpoint: true
17properties:
18  api:
19    type: "enum"
20    values: ["chat", "vision"]
21    default: "chat"
22  prepaidCredits:
23    type: "boolean"
24    default: true
25  videoUploadsPerDay:
26    type: "integer"
27    default: 50

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