Voyage AI

Hosted embedding and rerank models for retrieval.

Provider: default
Kind: AI service
Category: Compute
Official docs: https://docs.voyageai.com/docs/rate-limits
Also known as: Voyage API, Atlas Embedding API

Properties · 4 set by this component

property	type	values	required	kind default	this component
apiHost · component property	enum	voyageai \| mongodb-atlas	no	voyageai	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
endpoint · component property	enum	embeddings \| multimodal-embeddings \| contextualized-embeddings \| rerank	no	embeddings	inherited
keyStore	boolean	—	no	false	inherited
managed	boolean	—	no	false	▸ true
modality	enum	text \| vision \| speech \| multimodal \| structured \| image \| video \| audio \| embedding \| rerank	no	—	▸ embedding
publicEndpoint	boolean	—	no	—	▸ true
quotaUnitsPerMinute	integer	—	no	—	inherited
rateLimitRpm · advanced	integer	—	no	—	inherited
rateLimitTpm · advanced	integer	—	no	—	inherited
trainingOptOut · component property	boolean	—	no	false	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: "voyage-ai", component: "voyage-ai" }

Other AI service products · 125

and 85 more → AI service page

Source

1# yaml-language-server: $schema=../../schema/component.schema.json
2# Voyage AI: hosted text, multimodal and contextual embedding and rerank models; now part of MongoDB and also
3# served as the Atlas Embedding and Reranking API. Per "FAQ", data is kept for training unless an admin with a
4# payment method opts out; per "Rate Limits", Tier 1 needs a payment method and gives 2000 RPM and 8M TPM.
5schemaVersion: "1"
6type: "component"
7id: "voyage-ai"
8kind: "ai-service"
9provider: "default"
10docs: "https://docs.voyageai.com/docs/rate-limits"
11aliases: ["Voyage API", "Atlas Embedding API"]
12defaults:
13  auth: "api-key"
14  managed: true
15  modality: "embedding"
16  publicEndpoint: true
17properties:
18  trainingOptOut:
19    type: "boolean"
20    default: false
21  endpoint:
22    type: "enum"
23    values: ["embeddings", "multimodal-embeddings", "contextualized-embeddings", "rerank"]
24    default: "embeddings"
25  apiHost:
26    type: "enum"
27    values: ["voyageai", "mongodb-atlas"]
28    default: "voyageai"

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