Home›Agents›Manus Agent

AgentenCode evidence profileAutomation

✓ Editorially reviewedChecked: October 2, 2026

Agent profile · Automation

Manus Agent

Manus Agent is classified by AgentenCode as a general autonomous agent from Manus. 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.

ManusAutomationIndividuals & businesses

View profile ↓Check sources ↓

Automationeditorial classification

Manusprovider

11 primary sourcessource status

October 2, 2026last verification

AgentenTrust 2.0 · EU & governance evidence

Trust, privacy and control evidence for Manus Agent

Direct answer: AgentenCode currently documents 5 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 & data0 of 8 documentedResidency, training, retention, DPA, subprocessors and processing scope.

Security contextSecurity & access3 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

Manus provides a programmatic HTTP API with resource/action endpoints.

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

High confidence

API · Webhooks

Yes — documented

Manus supports outbound webhooks for task lifecycle events.

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

High confidence

Governance · Audit logs · API

Yes — documented

Manus exposes approved compliance/audit-oriented APIs for enterprise governance.

Scope: manus_enterprise_compliance_api · verified 2026-10-02 · Primary source ↗

High confidence

Governance · Audit logs · Available

Yes — documented

Manus Team/Enterprise provides audit logs.

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

High confidence

Governance · RBAC

Yes — documented

Manus Team uses documented role-based permissions for team administration and access.

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

High confidence

Governance · SCIM

Yes — documented

Manus documents SCIM as an enterprise/team capability.

Scope: manus_team_enterprise · verified 2026-10-02 · Primary source ↗

High confidence

Hosting · Managed

Yes — documented

Manus provides managed cloud execution environments for agent tasks.

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

High confidence

Security · Soc2 Type2

Yes — documented

Manus documents SOC 2 Type 2 certification.

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

Evidence-backed overview

What is Manus Agent?

Product-specific evidence for Manus Agent

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

SOC 2 Type 2

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

Primary source ↗

Audit Log API

Yes · Scope: manus_enterprise_compliance_api · verified 2026-10-02.

Primary source ↗

Audit Logs

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

Primary source ↗

RBAC

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

Primary source ↗

SCIM

Yes · Scope: manus_team_enterprise · verified 2026-10-02.

Primary source ↗

hosting · managed

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

3primary sources

8field-level evidence claims

5documented trust controls

3history 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

Manus Agent is documented under Automation and is associated with Manus. 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 2, 2026.

Trust coverage

5 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 Manus Agent

Manus Agent is classified as Allgemeiner autonomer Agent from Manus. 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.

Web- und Informationsaufgaben

This use case is part of the stored profile for Manus Agent. The related strength is “Autonome Planung komplexer Aufgaben”. In a production evaluation, the practical boundary to verify is: Credit-Verbrauch vor längeren Aufgaben berücksichtigen.

Websites und digitale Ergebnisse erstellen

This use case is part of the stored profile for Manus Agent. The related strength is “Breites Aufgabenspektrum”. In a production evaluation, the practical boundary to verify is: Lokale Datei- und Toolrechte bewusst vergeben.

Mehrstufige Automatisierung

This use case is part of the stored profile for Manus Agent. The related strength is “Agent API für Integrationen”. In a production evaluation, the practical boundary to verify is: Ergebnisse und ausgeführte Aktionen kontrollieren.

Arbeit mit lokalen Dateien und Tools

This use case is part of the stored profile for Manus Agent. The related strength is “Desktop-Zugriff auf autorisierte lokale Arbeitsbereiche möglich”. In a production evaluation, the practical boundary to verify is: Credit-Verbrauch vor längeren Aufgaben berücksichtigen.

What to verify before adoption

Credit-Verbrauch vor längeren Aufgaben berücksichtigen. Treat undocumented controls as Unknown and verify the exact plan, region and deployment scope.
Lokale Datei- und Toolrechte bewusst vergeben. Treat undocumented controls as Unknown and verify the exact plan, region and deployment scope.
Ergebnisse und ausgeführte Aktionen kontrollieren. 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.

October 2, 2026 · Source Maintenance
September 30, 2026 · Verification Update
September 28, 2026 · Initial

Official sources

This profile links 11 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 Manus Agent?

Manus Agent is listed by AgentenCode as an automation agent or agentic product from Manus.

How much trust evidence is documented for Manus Agent?

The current trust layer documents 5 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 2, 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.