Skip to main content
extract-data-v4

Read app data as JSON

Turn what a phone shows into structured data.
markets-v4

Same app, different markets

See what an app shows in another country.
test-and-prove-v4

Test a flow and keep proof

Run a test and keep video and screenshots.
drive-the-phone-v4

Drive the phone step by step

Read the screen and tap from your own code.
watch-and-alert-v4

Watch an app and get alerts

Get notified when something changes.
personal-phone-v4

Automate your own phone

Briefings and approved actions on your phone.
sign-up-codes-v4

Finish a sign-up that sends a code

Read email and SMS codes during a sign-up.
stream-phone-v4

Your work phone in the browser

Watch and control a phone from your browser.

Before you start

  1. Create a key on the API Keys page and export MOBILERUN_API_KEY=....
  2. Install pip install mobilerun-sdk or npm install @mobilerun/sdk, or connect the MCP server.
  3. Have a ready phone. Start a Cloud Android phone in the dashboard, or connect your own phone. Stop cloud phones when you’re done.
Each example includes a multi-phone version, whether that’s running tasks in parallel, comparing markets, or streaming a grid of phones.

Phones and add-ons

Run the examples on our phones or yours, and add what a use case needs.

Cloud Android

Pay per minute or a dedicated phone. Stop and resume keeps apps and logins.

Cloud iOS

A dedicated real iPhone, or a virtual iPhone billed per minute.

Your own phone

Connect your own Android phone to Mobilerun.

Proxies and countries

Residential IPs and GPS for other countries.

Mailboxes and numbers

Receive email and SMS codes during a flow.

Live stream in your app

Show a phone to your users and let them take over.
  • Many phones at once: examples include multi-phone variants. See Devices.
  • Logins: store app logins in Credentials and attach them to tasks. Never put passwords in prompts.
  • Your own apps: upload your APK to the app library and install it on any Cloud Android phone.
  • Events instead of polling: Webhooks send task.run.completed and task.run.failed to your backend.
  • Browser control: drive Chrome on the phone with Puppeteer or Playwright, see Browser automation.
  • Traffic inspection: see an app’s HTTP and WebSocket traffic while you walk its screens, see Network inspection.
  1. Ask what the user wants to build and match it to an example above. Start at Level 1.
  2. Use MCP if it’s connected; otherwise write SDK code.
  3. List phones and capabilities first. Ask before creating phones, proxies, mailboxes, numbers or webhooks, and never approve a purchase.
  4. Report the result, the steps, and anything that failed.
Never put passwords in prompts. Use Credentials.