Agent profile · Automation
Make AI Agents
Make AI Agents is classified by AgentenCode as a agent platform / builder from Make. 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.
AgentenTrust 2.0 · EU & governance evidence
Trust, privacy and control evidence for Make AI Agents
Direct answer: AgentenCode currently documents 9 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
Make Enterprise provides audit logs.
Scope: make_enterprise_including_ai_agents · verified 2026-10-01 · Primary source ↗Governance · Audit logs · Retention days
Make Enterprise audit logs are retained for 12 months (365 days).
Scope: make_enterprise_audit_logs · verified 2026-10-01 · Primary source ↗Governance · Custom roles
Make Enterprise supports custom roles.
Scope: make_enterprise · verified 2026-10-01 · Primary source ↗Governance · RBAC
Make Enterprise provides role-based access control.
Scope: make_enterprise_including_ai_agents · verified 2026-10-01 · Primary source ↗Governance · SSO · Oidc
Make Enterprise supports OIDC SSO.
Scope: make_enterprise_including_ai_agents · verified 2026-10-01 · Primary source ↗Governance · SSO · Saml
Make Enterprise supports SAML 2.0 SSO.
Scope: make_enterprise_including_ai_agents · verified 2026-10-01 · Primary source ↗Hosting · Managed
Make AI Agents run within Make's managed cloud platform.
Scope: make_ai_agents_cloud · verified 2026-10-01 · Primary source ↗Protocols · Mcp · Client
Make AI Agent (New) can act as an MCP client for configured MCP servers.
Scope: make_ai_agent_new · verified 2026-10-01 · Primary source ↗Security · Encryption · At rest
Make documents AES-256 encryption at rest.
Scope: make_platform_including_ai_agents · verified 2026-10-01 · Primary source ↗Security · Encryption · In transit
Make documents TLS 1.2/1.3 encryption in transit.
Scope: make_platform_including_ai_agents · verified 2026-10-01 · Primary source ↗Security · Soc2 Type2
Make documents SOC 2 Type II compliance.
Scope: make_platform_including_ai_agents · verified 2026-10-01 · Primary source ↗Evidence-backed overview
What is Make AI Agents?
Make AI Agents is classified by AgentenCode as a agent platform / builder from Make. 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.
Product-specific evidence for Make AI Agents
This profile links 7 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.
Verschlüsselung at rest
AES-256 · Scope: make_platform_including_ai_agents · verified 2026-10-01.
Primary source ↗Verschlüsselung in transit
TLS 1.2/1.3 · Scope: make_platform_including_ai_agents · verified 2026-10-01.
Primary source ↗Audit-Log-Aufbewahrung
365 · Scope: make_enterprise_audit_logs · 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
Make AI Agents is documented under Automation and is associated with Make. 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
9 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 Make AI Agents
Make AI Agents is classified as Agentenplattform / Builder from Make. 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.
Business-Automation
This use case is part of the stored profile for Make AI Agents. The related strength is “Visuelle Automationslogik”. In a production evaluation, the practical boundary to verify is: Tool-Berechtigungen begrenzen.
App-übergreifende Aufgaben
This use case is part of the stored profile for Make AI Agents. The related strength is “Großes Integrationsökosystem”. In a production evaluation, the practical boundary to verify is: Kosten durch Agentenläufe beobachten.
Operations
This use case is part of the stored profile for Make AI Agents. The related strength is “Agenten und klassische Workflows kombinierbar”. In a production evaluation, the practical boundary to verify is: Kritische Aktionen mit Freigaben absichern.
Interne Assistenten
This use case is part of the stored profile for Make AI Agents. The related strength is “Nachvollziehbare Tool-Nutzung”. In a production evaluation, the practical boundary to verify is: Tool-Berechtigungen begrenzen.
What to verify before adoption
- Tool-Berechtigungen begrenzen. Treat undocumented controls as Unknown and verify the exact plan, region and deployment scope.
- Kosten durch Agentenläufe beobachten. Treat undocumented controls as Unknown and verify the exact plan, region and deployment scope.
- Kritische Aktionen mit Freigaben absichern. 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 7 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.
- Make Help – AI Agents
- Make Help – Audit logs
- Make – Governance updates
- Make – Enterprise
- Make Help – Single Sign-on
- Make Help – Create your first AI agent
- Make – Security and Compliance
Frequently asked questions
What is Make AI Agents?
Make AI Agents is listed by AgentenCode as an automation agent or agentic product from Make.
How much trust evidence is documented for Make AI Agents?
The current trust layer documents 9 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.