OpenRouter

Single OpenAI-compatible endpoint that routes requests across many upstream model providers.

Provider: default
Kind: AI service
Category: Compute
Official docs: https://openrouter.ai/docs/api-reference/limits

Properties · 5 set by this component

property	type	values	required	kind default	this component
allowTrainingProviders · component property	boolean	—	no	—	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
modelVariant · component property	enum	free \| paid	no	paid	inherited
providerFallback · component property	boolean	—	no	true	inherited
publicEndpoint	boolean	—	no	—	▸ true
quotaUnitsPerMinute	integer	—	no	—	▸ 20
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: "openrouter", component: "openrouter" }

Other AI service products · 125

and 85 more → AI service page

Source

1# yaml-language-server: $schema=../../schema/component.schema.json
2# OpenRouter: single OpenAI-compatible endpoint that routes a request to one of many upstream model providers.
3# Per "Rate limits", free model variants allow 20 requests per minute (50 per day under $10 lifetime credits,
4# 1,000 above) and credit limits return 402; per "Privacy and logging", the account chooses whether requests
5# may be routed to providers that train on prompts, with separate settings for free and paid models.
6schemaVersion: "1"
7type: "component"
8id: "openrouter"
9kind: "ai-service"
10provider: "default"
11docs: "https://openrouter.ai/docs/api-reference/limits"
12defaults:
13  auth: "api-key"
14  managed: true
15  modality: "multimodal"
16  publicEndpoint: true
17  quotaUnitsPerMinute: 20
18properties:
19  allowTrainingProviders:
20    type: "boolean"
21  providerFallback:
22    type: "boolean"
23    default: true
24  modelVariant:
25    type: "enum"
26    values: ["free", "paid"]
27    default: "paid"

The same page as markdown, for an agent: /catalogue/components/openrouter.md