Perplexity API

Hosted Sonar models that answer from live web search with citations.

Provider: default
Kind: AI service
Category: Compute
Official docs: https://docs.perplexity.ai/docs/resources/privacy-security
Also known as: Sonar API

Properties · 5 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	—	▸ 0
endpoint · component property	enum	sonar \| agent \| search \| embeddings	no	sonar	inherited
keyStore	boolean	—	no	false	inherited
managed	boolean	—	no	false	▸ true
modality	enum	text \| vision \| speech \| multimodal \| structured \| image \| video \| audio \| embedding \| rerank	no	—	▸ text
publicEndpoint	boolean	—	no	—	▸ true
quotaUnitsPerMinute	integer	—	no	—	inherited
rateLimitRpm · advanced	integer	—	no	—	inherited
rateLimitTpm · advanced	integer	—	no	—	inherited
usageTier · component property	enum	tier-0 \| tier-1 \| tier-2 \| tier-3 \| tier-4 \| tier-5	no	tier-0	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: "perplexity-api", component: "perplexity-api" }

Other AI service products · 125

and 85 more → AI service page

Source

1# yaml-language-server: $schema=../../schema/component.schema.json
2# Perplexity API: hosted Sonar models that answer with live web search and citations, plus Search and Embeddings.
3# Per "Privacy & Security", Chat Completions data is not retained or used for training; only billing metadata
4# is kept. Per "Rate Limits & Usage Tiers", new accounts start on Tier 0 and tiers rise with lifetime spend.
5schemaVersion: "1"
6type: "component"
7id: "perplexity-api"
8kind: "ai-service"
9provider: "default"
10docs: "https://docs.perplexity.ai/docs/resources/privacy-security"
11aliases: ["Sonar API"]
12defaults:
13  auth: "api-key"
14  managed: true
15  modality: "text"
16  publicEndpoint: true
17  dataRetentionDays: 0
18properties:
19  usageTier:
20    type: "enum"
21    values: ["tier-0", "tier-1", "tier-2", "tier-3", "tier-4", "tier-5"]
22    default: "tier-0"
23  endpoint:
24    type: "enum"
25    values: ["sonar", "agent", "search", "embeddings"]
26    default: "sonar"

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