Agent profile · Research
Perplexity Deep Research
Perplexity Deep Research is classified by AgentenCode as a research mode / agent from Perplexity. It belongs to the Research category. This English profile does not maintain a separate factual record: it renders the same underlying evidence, trust and history data as the German profile.
This agent profile links to a curated provider view. Security controls are not inherited across products.
AgentenTrust 2.0 · EU & governance evidence
Trust, privacy and control evidence for Perplexity Deep Research
Direct answer: AgentenCode currently documents 8 of 36 normalized trust controls for this profile. Missing fields remain Unknown and are never automatically interpreted as “no”.
Important: these numbers show evidence coverage, not a product rating. 0 of 10 means that no field-level public evidence is stored for those ten controls in the current dataset. It does not mean the product lacks those capabilities.
Field-level evidence
Documented controls and values from primary sources.
Governance · Audit logs · Available
Perplexity Enterprise provides audit logs.
Scope: perplexity_enterprise_research · verified 2026-10-01 · Primary source ↗Governance · Custom roles
Perplexity Enterprise supports custom roles with granular permissions.
Scope: perplexity_enterprise · verified 2026-10-01 · Primary source ↗Governance · RBAC
Perplexity Enterprise provides role-based access controls.
Scope: perplexity_enterprise_research · verified 2026-10-01 · Primary source ↗Governance · SCIM
Perplexity Enterprise supports SCIM for the product suite including Research and Comet.
Scope: perplexity_enterprise_research · verified 2026-10-01 · Primary source ↗Governance · SSO · Saml
Perplexity Enterprise supports SAML SSO; this applies to Enterprise products including Research and Comet.
Scope: perplexity_enterprise · verified 2026-10-02 · Primary source ↗Hosting · Managed
Perplexity Deep Research is delivered as a managed Perplexity Computer capability.
Scope: perplexity_deep_research_in_computer · verified 2026-10-01 · Primary source ↗Security · Encryption · At rest
Perplexity documents AES-256 encryption at rest.
Scope: perplexity_enterprise_platform · verified 2026-10-01 · Primary source ↗Security · Encryption · In transit
Perplexity documents TLS 1.3 encryption in transit.
Scope: perplexity_enterprise_platform · verified 2026-10-01 · Primary source ↗Security · Soc2 Type2
Perplexity documents SOC 2 Type II compliance.
Scope: perplexity_enterprise_platform · verified 2026-10-01 · Primary source ↗Evidence-backed overview
What is Perplexity Deep Research?
Perplexity Deep Research is classified by AgentenCode as a research mode / agent from Perplexity. It belongs to the Research category. This English profile does not maintain a separate factual record: it renders the same underlying evidence, trust and history data as the German profile.
Product-specific evidence for Perplexity Deep Research
This profile links 5 unique primary sources across the product profile, field-level evidence, trust controls and documented relations. The points below describe this product’s stored evidence rather than generic characteristics of Recherche.
Verschlüsselung at rest
AES-256 · Scope: perplexity_enterprise_platform · verified 2026-10-01.
Primary source ↗Verschlüsselung in transit
TLS 1.3 · Scope: perplexity_enterprise_platform · verified 2026-10-01.
Primary source ↗AgentenCode treats this page as a reference profile rather than a ranking. Product facts are separated from editorial classification, and the profile is tied to a specific verification date. If a capability is not backed by sufficiently precise public evidence, it remains unknown instead of being inferred from marketing language or from similar products.
How to read the evidence
The field-level evidence layer records a value, a scope, a confidence level, a verification date and one or more primary sources. Scope matters: an enterprise-only security feature must not be generalized to every plan or deployment surface. The same rule applies to hosting, privacy, audit and protocol claims.
AgentenCode also keeps Unknown distinct from false. A missing claim means the public dataset does not currently contain sufficiently precise evidence for that field. A negative value is used only when a reliable primary source explicitly documents a restriction or non-availability.
Decision context
Provider and category
Perplexity Deep Research is documented under Research and is associated with Perplexity. Category labels help navigation but do not replace product-specific evidence.
Verification status
The public profile is marked editorially reviewed and was last checked on October 1, 2026.
Trust coverage
8 of 36 normalized trust controls currently have field-level public evidence. The remaining controls are not treated as negative findings.
Source-first use
For procurement, security or legal decisions, use the linked primary sources and verify the plan, region and configuration that apply to your organization.
Capabilities, strengths and deployment checks for Perplexity Deep Research
Perplexity Deep Research is classified as Recherchemodus / Agent from Perplexity. The profile’s editorial layer is derived from the stored use cases, strengths and checks below; claims about security, privacy or governance remain separate and require field-level evidence.
Marktrecherche
This use case is part of the stored profile for Perplexity Deep Research. The related strength is “Starker Fokus auf Webquellen”. In a production evaluation, the practical boundary to verify is: Research Mode und andere Perplexity-Modi unterscheiden.
Produktvergleich
This use case is part of the stored profile for Perplexity Deep Research. The related strength is “Zitierte Berichte”. In a production evaluation, the practical boundary to verify is: Planabhängige Limits und Datenquellen prüfen.
Lernen
This use case is part of the stored profile for Perplexity Deep Research. The related strength is “Niedrige Einstiegshürde”. In a production evaluation, the practical boundary to verify is: Primärquellen bei wichtigen Entscheidungen bevorzugen.
Schnelle Tiefenrecherche
This use case is part of the stored profile for Perplexity Deep Research. The related strength is “In Perplexity-Umgebungen weiterverarbeitbare Ergebnisse”. In a production evaluation, the practical boundary to verify is: Research Mode und andere Perplexity-Modi unterscheiden.
What to verify before adoption
- Research Mode und andere Perplexity-Modi unterscheiden. Treat undocumented controls as Unknown and verify the exact plan, region and deployment scope.
- Planabhängige Limits und Datenquellen prüfen. Treat undocumented controls as Unknown and verify the exact plan, region and deployment scope.
- Primärquellen bei wichtigen Entscheidungen bevorzugen. Treat undocumented controls as Unknown and verify the exact plan, region and deployment scope.
Verified history
The public history layer records only confirmed profile changes and verification events. Monitoring signals are not published as product facts until they have been reviewed.
- October 1, 2026 · Source Maintenance
- September 30, 2026 · Verification Update
- September 28, 2026 · Schema Upgrade
Official sources
This profile links 5 unique primary sources across the product profile, field-level evidence, trust layer and documented relations. Provider documentation remains authoritative when the product changes between verification cycles.
- Perplexity – Deep Research
- Perplexity Help – What is Enterprise Max?
- Perplexity – Role-based access controls, API credentials, Brain for Max
- Perplexity – Finding Alpha with Perplexity
- Perplexity – Enterprise security foundation
Frequently asked questions
What is Perplexity Deep Research?
Perplexity Deep Research is listed by AgentenCode as a research agent or agentic product from Perplexity.
How much trust evidence is documented for Perplexity Deep Research?
The current trust layer documents 8 of 36 normalized controls. Missing controls remain unknown rather than being treated as false.
When was this profile last checked?
The current profile verification date is October 1, 2026. The linked primary sources remain authoritative if the product changes between checks.