Home›Agents›Relevance AI Agents

AgentenCode evidence profileAutomation

✓ Editorially reviewedChecked: September 30, 2026

Agent profile · Automation

Relevance AI Agents

Relevance AI Agents is classified by AgentenCode as a agent platform / workforce from Relevance AI. It belongs to the Automation 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.

Relevance AIAutomationTeams & Businesses

View profile ↓Check sources ↓

Automationeditorial classification

Relevance AIprovider

9 primary sourcessource status

September 30, 2026last verification

AgentenTrust 2.0 · EU & governance evidence

Trust, privacy and control evidence for Relevance AI Agents

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”.

EU AI ActEvidence context only. AgentenCode does not infer legal applicability or compliance from individual product controls.

GDPRPrivacy and security signals are documented field by field. Data residency alone is not a compliance or transfer assessment.

Privacy contextPrivacy & data1 of 8 documentedResidency, training, retention, DPA, subprocessors and processing scope.

Security contextSecurity & access5 of 10 documentedEncryption, SSO, SCIM, RBAC, roles and credential handling.

Human controlHuman control0 of 10 documentedApproval, oversight, permissions and stop or rollback controls.

TraceabilityAudit & traceability2 of 8 documentedAudit logs, APIs, SIEM, observability, tracing and activity history.

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.

Documented yesDocumented valueUnknown remains unknown

High confidence

API · Rest

Yes — documented

Relevance AI exposes programmatic HTTP API access for agent execution and conversations.

Scope: relevance_ai_agents · verified 2026-10-01 · Primary source ↗

High confidence

API · Webhooks

Yes — documented

Relevance AI agents can be triggered through webhooks.

Scope: relevance_ai_agent_triggers · verified 2026-10-01 · Primary source ↗

High confidence

Governance · Audit logs · Available

Yes — documented

Relevance AI Enterprise provides audit logs.

Scope: relevance_ai_enterprise · verified 2026-10-01 · Primary source ↗

High confidence

Governance · Audit logs · SIEM export

Yes — documented

Enterprise audit logs and traces can be exported to customer-controlled observability/SIEM destinations through OpenTelemetry.

Scope: relevance_ai_enterprise_audit_stream · verified 2026-10-01 · Primary source ↗

High confidence

Governance · RBAC

Yes — documented

Relevance AI Enterprise supports role-based access control.

Scope: relevance_ai_enterprise · verified 2026-10-01 · Primary source ↗

High confidence

Governance · SSO · Saml

Yes — documented

Relevance AI Enterprise supports SAML SSO.

Scope: relevance_ai_enterprise · verified 2026-10-01 · Primary source ↗

High confidence

Hosting · Managed

Yes — documented

Relevance AI provides managed hosting and scaling for agents.

Scope: relevance_ai_platform · verified 2026-10-01 · Primary source ↗

High confidence

Privacy · Data residency · Available

Yes — documented

Relevance AI Enterprise documents data-residency capability.

Scope: relevance_ai_enterprise · verified 2026-10-01 · Primary source ↗

High confidence

Protocols · Mcp · Client

Yes — documented

Relevance AI agents can consume MCP-connected tools and servers.

Scope: relevance_ai_agents · verified 2026-10-01 · Primary source ↗

High confidence

Security · Encryption · At rest

Yes — documented

Relevance AI documents encryption at rest.

Scope: relevance_ai_platform_data · verified 2026-10-01 · Primary source ↗

High confidence

Security · Encryption · In transit

Yes — documented

Relevance AI documents encryption in transit.

Scope: relevance_ai_platform_data · verified 2026-10-01 · Primary source ↗

High confidence

Security · Soc2 Type2

Yes — documented

Relevance AI documents SOC 2 Type II compliance.

Scope: relevance_ai_platform · verified 2026-10-01 · Primary source ↗

Evidence-backed overview

What is Relevance AI Agents?

Product-specific evidence for Relevance AI Agents

This profile links 9 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 Automatisierung.

Data Residency

Yes · Scope: relevance_ai_enterprise · verified 2026-10-01.

Primary source ↗

Verschlüsselung at rest

Yes · Scope: relevance_ai_platform_data · verified 2026-10-01.

Primary source ↗

Verschlüsselung in transit

Yes · Scope: relevance_ai_platform_data · verified 2026-10-01.

Primary source ↗

SOC 2 Type 2

Yes · Scope: relevance_ai_platform · verified 2026-10-01.

Primary source ↗

Audit Logs

Yes · Scope: relevance_ai_enterprise · verified 2026-10-01.

Primary source ↗

SIEM Export

Yes · Scope: relevance_ai_enterprise_audit_stream · 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.

2primary sources

12field-level evidence claims

8documented trust controls

2history events

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

Relevance AI Agents is documented under Automation and is associated with Relevance AI. 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 September 30, 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 Relevance AI Agents

Relevance AI Agents is classified as Agentenplattform / Workforce from Relevance AI. 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.

Sales Ops

This use case is part of the stored profile for Relevance AI Agents. The related strength is “Agenten-Teams und Handoffs”. In a production evaluation, the practical boundary to verify is: Agentenrollen klar abgrenzen.

Research

This use case is part of the stored profile for Relevance AI Agents. The related strength is “Visueller Builder”. In a production evaluation, the practical boundary to verify is: Handoffs und Fehlerpfade testen.

Support

This use case is part of the stored profile for Relevance AI Agents. The related strength is “Tool- und Integrationsunterstützung”. In a production evaluation, the practical boundary to verify is: Datenzugriff pro Agent minimieren.

Multi-Agent-Workflows

This use case is part of the stored profile for Relevance AI Agents. The related strength is “Unternehmensprozesse im Fokus”. In a production evaluation, the practical boundary to verify is: Agentenrollen klar abgrenzen.

What to verify before adoption

Agentenrollen klar abgrenzen. Treat undocumented controls as Unknown and verify the exact plan, region and deployment scope.
Handoffs und Fehlerpfade testen. Treat undocumented controls as Unknown and verify the exact plan, region and deployment scope.
Datenzugriff pro Agent minimieren. Treat undocumented controls as Unknown and verify the exact plan, region and deployment scope.

Editorial boundary: The use-case and strength descriptions are product-specific editorial context based on the stored profile. Trust, privacy and governance statements are only presented as facts when field-level primary-source evidence exists.

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.

September 30, 2026 · Verification Update
September 28, 2026 · Schema Upgrade

Official sources

This profile links 9 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.

Frequently asked questions

What is Relevance AI Agents?

Relevance AI Agents is listed by AgentenCode as an automation agent or agentic product from Relevance AI.

How much trust evidence is documented for Relevance AI Agents?

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 September 30, 2026. The linked primary sources remain authoritative if the product changes between checks.

Method note: AgentenCode does not certify GDPR or EU AI Act compliance. It documents evidence that can support a separate legal, security or procurement assessment.