> ## Documentation Index
> Fetch the complete documentation index at: https://docs.mobilerun.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Limits and costs

> How credits are spent, how to estimate a job before running it, and what stops a run from getting out of hand.

## How credits are spent

Credits pay for the model usage behind everything your agent does. 1 credit equals \$0.01. A
plain conversation with your agent, with no device work, doesn't burn meaningful credits.

Credits are deducted in real time from the actual token cost of each model request. A run costs
more when it takes more steps, uses vision, or runs on a larger model. A step is one unit of work
your agent takes toward your goal, not one tap on the screen. A single step can bundle several
taps, screenshots, or waits together, so tightly described tasks cost less than vague, exploratory
ones.

> [!NOTE]
>
> Credits come from your plan, top-ups, and the phone add-ons that include credits (Cloud Android
> with a dedicated IP, Cloud iOS with a dedicated IP, and Personal Phone). The Cloud Android plan
> without a dedicated IP has no credits. Device minutes and residential traffic are
> separate meters with their own allowances. Top-up credits stay until you spend them. See
> [Credits & usage](https://docs.mobilerun.ai/credits.md) for how each meter works.

## Getting a cost estimate

You can ask your agent how much a task will cost before you run it. It gives you a rough
estimate based on how many steps the task is likely to take, not a hard quote. The only exact
number is what a run actually spends, which you can see on the task afterward or in your account
balance.

> Roughly how many credits would it cost to scrape this page every day?

> [!TIP]
>
> You can also ask your agent to explain how credits are counted, or to show you a breakdown of
> your recent usage, straight in the chat.

## What makes a job expensive

* **More steps.** A task that decides what to do screen by screen, using vision to figure out
  where to tap, takes more steps than one with a clear, repeatable path.
* **Loosely described goals.** "Check my accounts" takes more exploration than "open Instagram and
  check my DMs."
* **Extra devices.** One Cloud Android phone can usually run several accounts. Add a device only when you
  genuinely need separate isolation, such as a dedicated proxy per account.
* **Repeated retries.** If the same approach keeps failing, your agent treats that as a signal
  to change tactics or stop, rather than a reason to try the exact same thing again.

## Budgets that stop runaway jobs

Every task has a cap on how many steps it can take and how long it can run, so a stuck task can't
burn credits indefinitely. While it works, your agent also checks whether it's actually making
progress toward your goal. If a run stops advancing, it stops itself, reports what it achieved, and
tells you what's left, instead of looping.

A Pay as you go phone also stops billing on its own: when your device minutes run out, it is
stopped and keeps its data. A country proxy on that phone is billed as residential traffic (GB).

## What it refuses or hands to the dashboard

Your agent never buys, subscribes, upgrades, or adds credits on your behalf. Anything involving
money shows up as a card in the chat, and you complete it in the dashboard yourself. It does not quote
plan prices from memory; it shows you the current pricing card. For your balance, check the
Billing section of the dashboard.

## Plans, upgrades, and top-ups

Ask your agent what plans are available or how to add credits, and it shows you the relevant
card. See [Credits](https://docs.mobilerun.ai/credits.md) for how device subscriptions, credit allowances, and top-ups work.

## Related

> [card] [Credits](https://docs.mobilerun.ai/credits.md)
>
> The full credit system, device allowances, and top-up pricing.

> [card] [Overview](https://docs.mobilerun.ai/agents/overview.md)
>
> What your agent is and what it can do.

> [card] [Human in the loop](https://docs.mobilerun.ai/agents/human-in-the-loop.md)
>
> How approvals and questions pause a run mid-task.

> [card] [Getting started](https://docs.mobilerun.ai/agents/getting-started.md)
>
> Your first conversation and first result.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.