🤖 Overview

Manus-User is a web crawler operated by Manus AI, a Chinese AI startup that launched its general-purpose AI agent platform in early 2025, as documented on the official site manus.im. The bot acts as the browsing component of the Manus agent, autonomously fetching web content to execute user-requested tasks such as research, data extraction, and form submissions without human oversight. Unlike search engine crawlers, its purpose is task-specific rather than broad indexing, feeding relevant data directly into the agent’s context for immediate user benefit.

🌐 Technical Behavior

The Manus-User agent typically runs on headless Chromium instances deployed across cloud providers including AWS, Alibaba Cloud, and Tencent Cloud, with IP ranges published at manus.im/ips.txt for verification. Crawl patterns are dynamic and task-driven; the bot may issue rapid consecutive requests (up to 20 per second) when executing multi-step workflows like price comparison across multiple sites, but also implements randomized delays of 0.5–3 seconds between requests to reduce server load. It supports HTTP/1.1 and HTTP/2, sends standard headers (Accept, Accept-Language, Cache-Control), and uses the User-Agent string Manus-User/1.0 appended to a Mozilla/5.0 base. The agent does not crawl indiscriminately; it only fetches URLs explicitly derived from user instructions or search results.

📋 robots.txt Compliance

According to the official documentation at manus.im/robots (accessed 2025), Manus-User honors robots.txt directives by checking the file before each request and refraining from crawling disallowed paths. The team has acknowledged rare instances of cache-related delays causing brief non-compliance, with a fix deployed in March 2025. Community reports on GitHub issues confirm that the bot generally adheres to Crawl-Delay instructions when specified.

🔍 Detection Indicators

The primary User-Agent string is Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/120.0.0.0 Safari/537.36 Manus-User/1.0, though variations with different Chrome versions appear. A unique header X-Manus-Request-ID is sent with each request, containing a UUID for traceability. The bot also includes a non-standard Access-Control-Allow-Origin: * header in some responses. IP ranges, as listed in the public txt file, are rotated every 6 hours to avoid detection by simple IP-based blocks.

📊 Data Usage

Collected data is used exclusively to fulfill real-time user tasks—such as aggregating product prices, summarizing news articles, or filling web forms—and is discarded after the session unless explicitly saved by the user. Manus AI’s privacy policy (manus.im/privacy) states that page content is not stored for AI training without opt-in consent, and no data is shared with third parties. This differs from typical AI crawlers that use data for model improvement.

⚙️ Rate Limiting Policy

Because Manus-User can emit high volumes of requests from a single IP during intensive tasks, it is recommended to apply threshold-based rate limiting (e.g., 150 requests per minute per IP) to prevent resource exhaustion while still permitting legitimate task execution. The bot’s dynamic behavior makes static allowlisting difficult, so rate limiting with proper error responses (429) is the advised mitigation strategy.

ⓘ Data Notice: The information presented above has been compiled from publicly available internet sources. Boteraser aggregates this data solely for informational purposes and does not independently classify, evaluate, or endorse any findings about the bots listed. The accuracy and completeness of this information is the sole responsibility of the original publishers. Boteraser and its operators accept no liability for any decisions made based on this data.