Manus Access: Sign Up, Plans, and First Task
On this page
Quick answer
An invite or waitlist is no longer the default public access path described by Manus’s current site. The site links directly to the web app, desktop and mobile downloads, pricing, documentation, API, and Team plan. Use the live sign-up flow instead of buying codes or following old “waitlist acceleration” advice.
Before the first task, verify the account, plan, credits, concurrency, data policy, security settings, and connector permissions. Start with a public, reversible, low-cost task that does not require login or an external action.
Check current access
- Open the official Manus site and follow its current web or download path.
- Confirm the domain, region, account identity, workspace, and billing owner.
- Review the live pricing and Help Center; Manus currently documents Free, Pro, and Team options, but allocations and prices can change.
- Check whether the needed feature is tied to a plan, model, connector, app, API, or team setting.
- Enable available account-security controls and preserve recovery information through approved procedures.
Do not enter credentials into an unofficial invite marketplace or community form. A social post, referral claim, or old screenshot is not an access policy.
Choose a plan by workload
| Need | What to verify |
|---|---|
| Explore the product | Free-plan agent model, daily or monthly credits, concurrency and scheduled-task limits |
| Regular individual work | Pro model access, monthly credits, add-ons, concurrency, support and renewal behavior |
| Team use | Seats, shared credit pool, SSO, access control, audit or sharing controls, training opt-out and administration |
| Integration | Connector or API availability, token scopes, rate limits, cost and support |
Manus credits are consumed according to active task resources such as model tokens, virtual machines, and third-party APIs. Estimate the workload rather than comparing only the headline allocation.
Run a safe first task
Use a task such as:
From these three official public URLs, create a table of publication date, documented feature, lifecycle status, and one material caveat. Cite each row. Do not log in, follow external links, submit forms, or use personal data. Stop if a source is unavailable.
This task teaches source handling, output structure, stopping behavior, and credit use without granting meaningful external authority.
Review the result
Check:
- every URL was opened and belongs to the intended publisher;
- dates and lifecycle labels match the source;
- tables do not turn marketing language into independent fact;
- unavailable sources and uncertainty are visible;
- the task stayed within the approved site and action boundary; and
- the credit and runtime record are reasonable for the result.
Only then expand to more sources, files, code, or connectors.
Add connectors deliberately
Manus documents connectors for services including email, calendars, development tools, project systems, databases, and MCP servers. For each connection, record:
- the exact user or workspace;
- read and write scopes;
- data categories and prohibited fields;
- whether results can appear in shared sessions;
- token storage and revocation;
- confirmation rules for external changes; and
- the owner who reviews access over time.
Manus says shared sessions hide connector output and redact sensitive information such as API keys, while also warning users to be careful about shared content. Treat redaction as defense in depth, not permission to share secrets.
Frequently asked questions
Do I still need a Manus invite code?
The public Manus site now links directly to its web app, downloads, pricing, documentation, and team plan. Do not pay for or rely on an old invite guide; check the live sign-up flow for your account, region, and workspace.
Which Manus plan should a new user choose?
Start by checking the live Free, Pro, and Team plan pages against required models, credits, concurrency, scheduled tasks, connectors, administration, and data controls. Do not choose from an old price screenshot.
What is a safe first Manus task?
Use a reversible public-web research task with a fixed source list, no login, no personal data, no purchase or message, a small credit budget, and a deliverable that can be checked manually.
Should I connect email or work tools during onboarding?
Only after reviewing the exact connector scopes, account, data exposed, write permissions, sharing behavior, revocation path, and organizational approval. Product access is not connector authorization.
Continue by task
- Understand what Manus is now.
- Review the current credits, security, and connectors FAQ.
- Compare Manus with Flowith for research.
- Design human review into the productivity stack.
Official sources
- Manus
- Manus pricing
- Manus Help Center: current membership pricing
- Manus credits
- Manus connectors documentation
Source check: August 11, 2026. Recheck access, regions, plan names, prices, credits, models, concurrency, connector scopes, and account controls before sign-up or upgrade.