Credit Rule (rules for credits consumption)

Manus · Official agreement

Read the agreement

25 of 25 cards

Legal Rights & Agreement Rules · Context

The page is marked only "Updated today", with no calendar date

The credits article carries the label "Updated today" and gives no effective date, version number or update date, so the date of the text as read is not stated in the document itself.

Supporting quotations

Updated today

Not stated here

  • The calendar date this label referred to is not given in the document.

Charges & Financial Obligations · Company practice

Credits are mainly spent on LLM tokens, virtual machines and third-party APIs

Manus says credits are primarily consumed based on three things: LLM tokens (task planning, decision making and output generation), virtual machines (cloud environments for file operations, browser automation and code execution) and third-party APIs (access to integrated external services, such as financial data and professional databases). The word "primarily" means these are the main bases for consumption; the passage does not say the list is exhaustive.

Supporting quotations

Credits are primarily consumed based on:
LLM tokens: Used for task planning, decision making, and output generation.
Virtual machines: Used for cloud environments that support file operations, browser automation, and code execution.
Third-party APIs: Used for accessing integrated external services, such as financial data and professional databases.

Qualifications & exceptions

  • The list is introduced as what credits are "primarily" consumed on, not as a complete list.

Not stated here

  • How many credits an LLM token, a period of virtual-machine use or a third-party API call costs is not stated.

Charges & Financial Obligations · Company practice

The credits a task uses depend on its complexity and duration, counted only while it is actively processing

Manus states that the specific number of credits a task consumes is determined by the task's complexity and duration, and that credits are consumed only during active task processing.

Supporting quotations

The specific credits consumption for a task is determined by its complexity and duration. Credits are only consumed during active task processing.

Not stated here

  • No formula, rate or example task cost is given, and what counts as "active task processing" is not defined.
Also annotated in the same passage (1)

Charges & Financial Obligations · Company practice

Completed tasks and the storage or deployment of their outputs use no credits

Manus says completed tasks, and the storage or deployment of their outputs, do not consume any credits, so a user does not need to delete completed tasks to save credits.

Supporting quotations

Completed tasks and the storage or deployment of their outputs do not consume any credits, so there's no need to delete completed tasks.
Also annotated in the same passage (1)

Charges & Financial Obligations · Company commitment

Manus gives a full refund of the credits consumed by tasks that fail because of technical issues on its end

Manus states that it provides a full refund of consumed credits for tasks that fail due to technical issues on its end. The passage speaks of refunding credits consumed, not money.

Supporting quotations

We provide a full refund of consumed credits for tasks that fail due to technical issues on our end.

Qualifications & exceptions

  • Covers only tasks that fail due to technical issues on Manus's end; this passage does not say what happens to credits for tasks that fail for other reasons.

Not stated here

  • What counts as a technical issue on Manus's end is not defined.
  • The passage does not say how the refund is applied (for example, whether the credits are returned to the balance automatically) or whether a user must report the failure.
Also annotated in the same passage (1)

Charges & Financial Obligations · Company commitment

Manus says it will keep optimizing efficiency to reduce credits used per task

Manus says it will continuously optimize system efficiency and reduce the number of credits consumed per task. This is a general statement of intent.

Supporting quotations

We will continuously optimize system efficiency and reduce the number of credits consumed per task.

Not stated here

  • No target, timeline or measure is given, and the passage does not say that any past or future reduction would apply to credits already spent.
Also annotated in the same passage (1)

Charges & Financial Obligations · Procedure

Free users can upgrade to Pro, and members can switch to a higher plan, to get more credits

Manus says Free users can upgrade to a Pro membership for more credits, and members who need additional credits can switch to a higher plan. The passage points to Manus's pricing page for membership benefits and upgrading to a paid plan.

Supporting quotations

For Free users, you can upgrade to a Pro membership for more credits.
Members who need additional credits can switch to a higher plan.
To learn more about membership benefits or to upgrade to a paid plan

Not stated here

  • Plan prices and credit amounts are not in this document; the pricing page it links to is not supplied.
  • This section does not mention add-on credit packs as a way to get more credits; the document describes add-on credits separately.

Charges & Financial Obligations · Company practice

Credits are spent in a fixed order: event, daily, monthly, add-on, then free

Manus states that credits are consumed in this order: event credits, then daily credits, then monthly credits, then add-on credits, then free credits.

Supporting quotations

Credits are consumed in the following order: event credits > daily credits > monthly credits > add-on credits > free credits.

Not stated here

  • The passage does not explain the reason for the order or how it interacts with each credit type's expiry.

Charges & Financial Obligations · Restriction or exception

Daily refresh credits are capped at 1,500 a month for Free users and can only be used for Manus 2.0 lite

Manus sets a monthly consumption limit of 1,500 credits on daily refresh credits for Free users; paid users have no limit. Daily credits can only be used for Manus 2.0 lite.

Supporting quotations

The monthly consumption limit for daily refresh credits for free users is set to 1,500 credits; paid users have no limit.
Daily credits can only be used for Manus 2.0 lite.

Not stated here

  • How many daily credits are granted each day is not stated; the related article on daily refresh credits that the page links to is not supplied.
  • The passage uses both "daily refresh credits" and "daily credits" and does not say whether they are the same thing.

Charges & Financial Obligations · Restriction or exception

Monthly credits come with a subscription and must be used within the monthly cycle

Monthly credits are obtained through a subscription and refresh automatically on the same date each month, based on the subscription date. They must be used within the subscription period. Manus's example is a $20 Pro membership bought on January 1st, which gives 4000 monthly credits that need to be used before February 1st, when unused credits reset. Unused credits from the previous month do not roll over and are cleared at the start of the new cycle. Upgrading to a higher plan during a billing cycle does not change the original cycle end date.

Supporting quotations

Monthly credits are obtained through subscription and automatically refresh on the same date each month based on your subscription date.
Monthly credits need to be used within the subscription period.
If not used up, they will reset on February 1st.
Unused credits from the previous month do not roll over and are cleared at the start of the new cycle.
Upgrading to a higher plan during a billing cycle does not alter the original cycle end date.

Qualifications & exceptions

  • The $20 Pro membership with 4000 credits is given as an example; the document says the credits allocated per cycle depend on your specific plan.

Not stated here

  • The credit allocation for each plan is not listed in this document.
Also annotated in the same passage (2)

Charges & Financial Obligations · Restriction or exception

Add-on credits can only be used with an active paid subscription, and unused ones can carry over until they expire

Manus says add-on credits require an active paid subscription to be used. Unused add-on credits can carry over between subscription cycles until they expire.

Supporting quotations

Add-on credits require an active paid subscription to be used. Unused add-on credits can carry over between subscription cycles until they expire.

Not stated here

  • The passage does not say whether a paid subscription is needed to buy add-on credits, only to use them.
  • How add-on credits are priced or purchased is not stated here.

Cross-references

  • contrast (model-proposed): Unused subscription credits do not roll over to the next cycle — Unused subscription credits are cleared at each cycle and do not roll over, while unused add-on credits can carry over between subscription cycles until they expire; the document separates them by saying add-on credits follow their own expiry rules.

Charges & Financial Obligations · Restriction or exception

New add-on credit packs last one year; existing packs expire on 31 December 2027

Manus states that new add-on credit packs have a one-year validity period, and existing add-on credit packs have been assigned an expiry date of 31 December 2027. Having an active subscription does not prevent add-on credits from expiring, and Manus asks users to use them before their expiry date.

Supporting quotations

New add-on credit packs have a one-year validity period.
Existing add-on credit packs have been assigned an expiry date of 31 December 2027.
An active subscription does not prevent add-on credits from expiring. Please use them before their expiry date.

Qualifications & exceptions

  • An active subscription does not stop add-on credits from expiring.

Not stated here

  • Which packs count as "new" and which as "existing", and when a new pack's one-year period starts (for example at purchase), are not stated.

Charges & Financial Obligations · Restriction or exception

Add-on credits become inactive when the paid subscription ends or the account moves to Free

If a paid subscription ends or the account switches to the Free plan, remaining add-on credits become inactive. They can be used again after renewing a paid subscription, but only if they have not expired.

Supporting quotations

If your paid subscription ends or your account switches to the Free plan, your remaining add-on credits become inactive. You can use them again after renewing a paid subscription, provided they have not expired.

Qualifications & exceptions

  • Reactivation requires renewing a paid subscription and depends on the credits not having expired.

Charges & Financial Obligations · Company practice

Free credits never expire; event credits expire when the event ends

Manus states that free credits never expire, and that event credits, which are earned by participating in events, expire when the event ends.

Supporting quotations

Free credits never expire.
Event credits can be earned by participating in events and expire when the event ends.

Not stated here

  • The document does not define "free credits" separately from daily refresh credits, and it does not say how long the daily credits last once granted.

Charges & Financial Obligations · Company practice

A task's last action can push the credit balance below zero, which Manus calls expected

Manus calculates and deducts the cost of each action at the start of the following action. In rare cases a task may therefore complete an action whose cost slightly exceeds the remaining credit balance, and the balance may temporarily show a negative value. Manus says this is expected behavior, does not indicate an error and does not require any action by the user. A negative balance means the final action of a task consumed more credits than remained at the time of deduction. This applies to all plan types, including Free, Pro and Team plans.

Supporting quotations

To ensure accurate credit accounting, Manus calculates and deducts the cost of each action at the start of the following action.
In rare cases, this means a task may complete an action whose cost slightly exceeds your remaining credit balance.
When this occurs, your credit balance may temporarily show a negative value. This is expected behavior and does not indicate an error or require any action on your part.
This applies to all plan types, including Free, Pro, and Team plans.
A negative balance simply means the final action of a task consumed more credits than you had remaining at the time of deduction.

Qualifications & exceptions

  • Described as happening in rare cases and when an action's cost slightly exceeds the remaining balance; applies to Free, Pro and Team plans.

Not stated here

  • The passage does not say how far below zero a balance can go beyond "slightly", or whether any extra charge applies to a negative balance; the document lists that question in its FAQ links but gives no answer.

Cross-references

Charges & Financial Obligations · Company practice

A negative credit balance is resolved automatically at the next credit refresh

Manus says negative balances are automatically resolved when credits next refresh.

Supporting quotations

Negative balances are automatically resolved when your credits next refresh.

Not stated here

  • The passage does not say how the refresh clears the negative amount, or whether buying more credits or upgrading would resolve it sooner.

Charges & Financial Obligations · Restriction or exception

New tasks cannot be started while available credits are at or below zero

Manus says users will not be able to start new tasks while their effective available credits are at or below zero.

Supporting quotations

You will not be able to start new tasks while your effective available credits are at or below zero.

Not stated here

  • "Effective available credits" is not defined, so the document does not say which credit types count toward it.

Cross-references

Charges & Financial Obligations · Restriction or exception

The refresh rules cover credits included in a subscription; add-on credits keep their own expiry rules

Manus says its credits refresh on a recurring cycle tied to the subscription, and that the timing depends on whether the plan is monthly or annual. At the start of each new cycle credits are replenished and unused credits from the previous cycle are cleared. These refresh rules apply to credits included in the subscription; add-on credits follow their own expiry rules and are not cleared just because a new monthly subscription cycle begins.

Supporting quotations

The refresh rules below apply to credits included in your subscription. Add-on credits follow their own expiry rules and are not cleared simply because a new monthly subscription cycle begins.
Manus credits refresh on a recurring cycle tied to your subscription.
At the start of each new cycle, your credits are replenished, and any unused credits from the previous cycle are cleared.

Qualifications & exceptions

  • Applies to credits included in the subscription, not to add-on credits.

Not stated here

  • The passage does not say whether daily, free or event credits count as "credits included in your subscription".
Also annotated in the same passage (1)

Charges & Financial Obligations · Company practice

Monthly subscriptions refresh credits on the same calendar date each month

For monthly subscriptions, credits refresh on the same calendar date each month, based on the subscription start date. Manus's example is a subscription that began on the 13th, whose credits refresh on the 13th of each following month. The number of credits allocated per cycle depends on the specific plan.

Supporting quotations

For monthly subscriptions, credits refresh on the same calendar date each month, based on your subscription start date.
For example, if your subscription began on the 13th of a month, your credits will refresh on the 13th of each subsequent month.
The number of credits allocated per cycle depends on your specific plan.

Not stated here

  • The document does not say what date applies in a month that lacks the subscription start day (for example a start on the 31st).
  • The credit allocation for each plan is not listed in this document.

Cross-references

Also annotated in the same passage (1)

Charges & Financial Obligations · Restriction or exception

Annual subscriptions refresh credits monthly, and all remaining credits reset when the year ends

On an annual subscription, credits refresh monthly during the subscription term, on the same calendar date each month based on the subscription start date. Unused credits are cleared at the end of each monthly cycle and do not roll over. At the end of the annual subscription period all remaining credits are reset, and Manus advises using credits within the subscription term to avoid losing them.

Supporting quotations

If you are on an annual subscription, your credits refresh monthly during the subscription term.
Unused credits are cleared at the end of each monthly cycle and do not roll over.
At the end of the annual subscription period, all remaining credits are reset.

Qualifications & exceptions

  • The monthly clearing applies within an annual term, not only at the end of the year.

Not stated here

  • The number of credits an annual plan allocates each month is not stated.

Charges & Financial Obligations · Company practice

Upgrading mid-cycle keeps the original refresh date and adds credits for the plan difference

Upgrading to a higher plan during a billing cycle does not change the original cycle end date, so credits still refresh on the same calendar date. Unused credits from the previous cycle are cleared on the original renewal date even if the plan was upgraded mid-cycle. When the new cycle begins, the user receives the allocation for the upgraded plan. On a mid-cycle upgrade the system also issues credits for the difference between the two plans, based on the remaining time of the current plan after the user upgrades and pays.

Supporting quotations

Upgrading to a higher plan during a billing cycle does not alter the original cycle end date. Your credits will still refresh on the same calendar date as before.
When the new cycle begins, you will receive the updated credit allocation associated with your upgraded plan.
unused credits from the previous cycle are cleared on the original renewal date, even if you upgrade mid-cycle.
When you upgrade mid-cycle, the system will issue the credits for the difference between the two plans based on the remaining time of your current plan after you upgrade and pay.

Qualifications & exceptions

  • The extra credits are calculated from the remaining time of the current plan after the user upgrades and pays.

Not stated here

  • The exact calculation of the difference credits is not given, and the passage does not say how the difference credits are treated at the next refresh.
Also annotated in the same passage (1)

Charges & Financial Obligations · Restriction or exception

Unused subscription credits do not roll over to the next cycle

Manus does not allow unused subscription credits to roll over. At the start of each new cycle all unused subscription credits are cleared and replaced with that cycle's allocation. This applies to both monthly and annual subscriptions. Add-on credits follow their own expiry rules and are not cleared simply because a new monthly subscription cycle begins.

Supporting quotations

Manus does not allow unused subscription credits to roll over to the next cycle.
At the start of each new cycle, all unused subscription credits are cleared and replaced with the new allocation for that cycle.
This policy applies to both monthly and annual subscriptions.
Add-on credits follow their own expiry rules and are not cleared simply because a new monthly subscription cycle begins.

Qualifications & exceptions

  • Applies to subscription credits; add-on credits are carved out under their own expiry rules.

Cross-references

Also annotated in the same passage (1)

Charges & Financial Obligations · Company practice

Credit purchases and credit refreshes follow UTC+0 time

Manus notes that both credit purchases and credit refreshes follow the UTC+0 timezone.

Supporting quotations

Please note that both credit purchases and credit refreshes follow the UTC+0 timezone.

Not stated here

  • The passage does not say how this affects a user in a timezone far from UTC+0, beyond naming the timezone.

Charges & Financial Obligations · Restriction or exception

Google Play subscribers: credits still refresh monthly, but the final period can be prorated

For Google Play subscriptions, upgrades add up subscription time, so a subscription cycle can exceed one month, but credits are still refreshed monthly. If proration leaves the last credit refresh cycle shorter than one full month, the credits issued for that final period are prorated: remaining duration divided by the month's total duration, multiplied by the total monthly credits.

Supporting quotations

Google Play subscriptions will have time accumulation in upgrade scenarios, causing subscription cycles to exceed one month, but credits are still refreshed monthly.
If proration leads to the last credit refresh cycle being less than one full month, the credits issued for that final period will be prorated based on the remaining time.
(Remaining duration/total duration of the month * total monthly credits)

Qualifications & exceptions

  • Applies only to subscriptions bought through Google Play, in upgrade scenarios where proration shortens the last refresh cycle.

Not stated here

  • The passage does not say how this proration works alongside the difference credits issued on a mid-cycle upgrade, or whether other app stores follow the same rule.

Cross-references