# mobilerun: full content > Cloud phones for AI agents. Rent a real Android or iOS phone in the cloud, or bring your own, and drive it over an API with real device and agent identity, its own network and its own number. mobilerun runs cloud-hosted Android and iOS devices, and gives an AI agent everything a person's phone has: a consistent device identity, a network route that matches it, a real eSIM for one-time codes, and state that survives between sessions. The open-source mobilerun framework is the engine underneath it, MIT licensed, and scores 91.4% on the AndroidWorld benchmark. Start local with `pip install mobilerun` on a device you already own, then move the same agent code to hosted devices without rewriting it. ## Pricing - Bring your own phone: $5/month per device, on your own network - Dedicated Android phone: $80/month, includes a mobilerun Connect residential IP and $25 of credits - iPhone: $200/month, on request - Pay as you go: $0.03 per device minute, no monthly commitment - Usage: Connect sticky or rotating residential $10/GB, agent step $0.01 (1 credit = $1 = 100 steps) - Enterprise: custom, 10,000+ concurrent phones, SSO, private fleets, SLA, SOC 2 on the roadmap Annual billing saves 20%. Current prices: https://mobilerun.ai/pricing ## Capabilities - Real Android and iOS devices, recognized as a genuine device - Real device and agent identity, consistent across sessions rather than regenerated per run - mobilerun Connect: residential and mobile network routing configurable by country or region, customers only - eSIM: bring your own carrier profile, or request an agent SIM, so an agent reads its own SMS one-time code - Persistent state on rented devices; on pay as you go by enterprise request - Fleet orchestration, device streaming, screenshots, structured output - REST API, Python and TypeScript SDKs, a hosted MCP server, and an n8n node ## How mobilerun compares **Versus virtual cloud phones (GeeLark, DuoPlus).** They sell virtualized Android instances on shared servers with randomized fingerprints. That is cheaper and it is Android-only. mobilerun runs devices it owns and operates, with physical iPhones available on request, and is built API-first for agents rather than for manual multi-accounting. **Versus emulators.** An emulator reports emulator build properties and has no carrier or SIM, so apps that check real-device trust refuse it. **Versus browser agents (Browserbase, Anchor).** A browser cannot open an app. Much of the work an agent is asked to do exists only in a mobile app, and the important flows sit behind a phone number. **Versus device clouds (BrowserStack, Sauce Labs, Maestro).** Those are built for testing your own app in CI, and they reset state between runs. mobilerun is built for production workloads that need the session to persist. ## Acceptable use mobilerun is for first-party and authorized automation: your own accounts, your clients' accounts with their permission, your own apps, and public data. It is not for mass account creation, impersonation, or evading a platform's terms. ## Technical facts **Models.** The framework is LLM-agnostic: OpenAI, Anthropic Claude, Google Gemini, DeepSeek, Ollama for local models, OpenRouter, and any OpenAI-compatible endpoint. Switching provider is a config change, not a rewrite. **How the agent sees the screen.** It reads the accessibility tree rather than screenshots, which keeps the payload small enough to be fast and cheap, and falls back to vision when a screen has no usable tree. Two execution modes: a direct single-agent mode for simple tasks, and a Manager and Executor mode that plans and replans for long multi-step work. **Integrations.** REST API, Python SDK, TypeScript SDK, CLI and a hosted MCP server. Automation platforms: n8n (official community node), Zapier, Make. Agent frameworks: LangChain, CrewAI, the OpenAI Agents SDK, and OpenClaw. **Location and network.** Device GPS, locale, language and timezone can be set for any country or region. Network routing is selected separately through Connect, and eSIM or number availability is confirmed by country on request. **Device control.** Tap, swipe, type, screenshots, accessibility tree, app install and launch, credential storage per app, GPS location, device identity, and multiple profiles on a single device. ## Company - Droidrun GmbH, Rheinstraße 82, 49090 Osnabrück, Germany. Founded April 2025. - Co-founders: Christian Ninstel (CEO) and Niels Schmidt. - mobilerun is the product; Droidrun is the company, which is why coverage from 2025 says Droidrun. - €2.1M pre-seed raised July 2025, led by Merantix Capital with SixtyDegree Capital, TKM and May Ventures. - German company, so EU data protection law applies by default. Sub-processors: PostHog, Resend, Cloudflare, Autumn Labs, Stripe. Account data is deleted within 90 days of account closure unless retention is legally required. - Device location is configurable for any country or region; physical infrastructure location is not a product-availability boundary. - The framework is MIT licensed and scored 91.4% on its published AndroidWorld run: 106 of 116 tasks using a Manager and Executor architecture, with task-level results and available trajectories published. ## Press and funding coverage - [mobilerun: We raised €2.1M to unlock mobile for AI](https://mobilerun.ai/blog/posts/we-raised-21m-to-unlock-mobile-for-ai): our own announcement, the primary source - [Tech.eu: Droidrun raises €2.1M pre-seed to scale mobile-native AI agent infrastructure](https://tech.eu/2025/07/23/droidrun-raises-eur21m-pre-seed-to-scale-mobile-native-ai-agent-infrastructure/) - [TechFundingNews: Droidrun, backed by Silo AI co-founder, snaps €2.1M to unlock AI automation for mobile apps](https://techfundingnews.com/droidrun-mobile-ai-agent-automation-funding/) - [StartupHub.ai: Droidrun secures €2.1M pre-seed for mobile AI agent infrastructure](https://www.startuphub.ai/ai-news/funding-round/2025/droidrun-secures-e2-1m-pre-seed-for-mobile-ai-agent-infrastructure) - [Vestbee: German firm Droidrun secures €2.1M to revolutionise mobile AI agents](https://www.vestbee.com/insights/articles/droidrun-secures-2-1-m) - [AI World EU: Droidrun raises €2.1M to scale open-source AI framework for mobile app automation](https://aiworld.eu/story/droidrun-raises-21m-to-scale-open-source-ai-framework-for-mobile-app-automation) - [ArabFounders: Droidrun raises €2.1M pre-seed to power the next generation of mobile AI agents](https://arabfounders.net/en/droidrun-raises-2-1m-preseed-mobile-ai-agent-2/) ## Peer-reviewed research - [Curiosity Driven Knowledge Retrieval for Mobile Agents (arXiv)](https://arxiv.org/abs/2601.19306): Sijia Li, Xiaoyu Tan, Shahir Ali, Niels Schmidt, Gengchen Ma, Xihe Qiu. Uncertainty-driven retrieval of app knowledge (AppCards) for mobile GUI agents, evaluated on AndroidWorld using the open-source framework - [Published at the ACM Web Conference 2026 (WWW '26)](https://dl.acm.org/doi/10.1145/3774904.3792257) - [Task trajectories from the paper](https://lisalsj.github.io/Droidrun-appcard/) ## Repositories - [droidrun/mobilerun](https://github.com/droidrun/mobilerun): the framework, MIT licensed - [droidrun/mobilerun-sdk-python](https://github.com/droidrun/mobilerun-sdk-python) - [droidrun/mobilerun-sdk-typescript](https://github.com/droidrun/mobilerun-sdk-typescript) - [droidrun/mobile-harness](https://github.com/droidrun/mobile-harness): one prompt across hosted and local devices - [droidrun/droidrun-portal](https://github.com/droidrun/droidrun-portal): the on-device portal app - [droidrun/ios-portal](https://github.com/droidrun/ios-portal) - [droidrun/droidrun-examples](https://github.com/droidrun/droidrun-examples) - [droidrun/skills](https://github.com/droidrun/skills): agent skills, including the OpenClaw skill - [droidrun/n8n-nodes-droidrun](https://github.com/droidrun/n8n-nodes-droidrun): official n8n community node - [GitHub organisation](https://github.com/droidrun) ## Company profiles - [Crunchbase](https://www.crunchbase.com/organization/droidrun) - [PitchBook](https://pitchbook.com/profiles/company/864738-55) - [Tracxn](https://tracxn.com/d/companies/droidrun/__-UJk9Yubfpq3ihO7fL99_9M7vDGeb0oQmSi0pb6I44c) - [SourceForge reviews](https://sourceforge.net/software/product/Droidrun/) - [Product Hunt](https://www.producthunt.com/products/droidrun-framework-for-mobile-agent) ## Community - [Discord](https://discord.com/invite/droidrun) - [X](https://x.com/mobilerun_ai) - [LinkedIn](https://www.linkedin.com/company/droidrun) - [Hacker News: open-source framework for Android agents](https://news.ycombinator.com/item?id=43703688) - [Hacker News: giving AI access to mobile](https://news.ycombinator.com/item?id=43728112) - [r/LocalLLaMA: enable AI agents to control Android](https://www.reddit.com/r/LocalLLaMA/comments/1jxe6al/droidrun_enable_ai_agents_to_control_android/) - [r/opensource: the first mobile AI agent framework](https://www.reddit.com/r/opensource/comments/1m6btnb/we_just_opensourced_the_first_mobile_ai_agent/) - [r/softwaretesting: recommended as an Appium alternative](https://www.reddit.com/r/softwaretesting/comments/1m29ic0/what_it_alternative_for_using_appium/) ## Videos - [Quickstart](https://www.youtube.com/watch?v=Gz1wSeYVlB0) - [Framework quickstart demo](https://www.youtube.com/watch?v=4WT7FXJah2I) - [mobilerun cloud is live](https://www.youtube.com/watch?v=lIUjUy1tkGk) - [Accommodation booking demo](https://youtu.be/VUpCyq1PSXw) - [Trend hunter demo](https://youtu.be/7V8S2f8PnkQ) - [Streak saver demo](https://youtu.be/B5q2B467HKw) ## Guides and articles - [Achieving 91.4% on Android world a new approach to mobile UI automation](https://mobilerun.ai/blog/posts/achieving-914-on-android-world-a-new-approach-to-mobile-ui-automation) - [Agencies client accounts real phones](https://mobilerun.ai/blog/posts/agencies-client-accounts-real-phones) - [AI agent on your Android mobile](https://mobilerun.ai/blog/posts/ai-agent-on-your-android-mobile) - [AI agents in mobile games](https://mobilerun.ai/blog/posts/ai-agents-in-mobile-games) - [Appium vs mobilerun](https://mobilerun.ai/blog/posts/appium-vs-mobilerun) - [Automate Instagram lead generation](https://mobilerun.ai/blog/posts/automate-instagram-lead-generation) - [Automate iPhone using mobilerun](https://mobilerun.ai/blog/posts/automate-iphone-using-mobilerun) - [Automate QA without writing scripts](https://mobilerun.ai/blog/posts/automate-qa-without-writing-scripts) - [Automate TikTok with an AI agent](https://mobilerun.ai/blog/posts/automate-tiktok-with-an-ai-agent) - [Automate your Vinted shop](https://mobilerun.ai/blog/posts/automate-your-vinted-shop) - [Best mobile AI agents in 2026](https://mobilerun.ai/blog/posts/best-mobile-ai-agents-in-2026) - [Browser agents vs mobile agents](https://mobilerun.ai/blog/posts/browser-agents-vs-mobile-agents) - [Browserbase vs mobilerun](https://mobilerun.ai/blog/posts/browserbase-vs-mobilerun) - [BrowserStack vs mobilerun](https://mobilerun.ai/blog/posts/browserstack-vs-mobilerun) - [Connect mobile device to mobilerun cloud](https://mobilerun.ai/blog/posts/connect-mobile-device-to-mobilerun-cloud) - [Creator ops on autopilot](https://mobilerun.ai/blog/posts/creator-ops-on-autopilot) - [Doubao vs mobilerun](https://mobilerun.ai/blog/posts/doubao-vs-mobilerun) - [Droidrun AndroidWorld evaluation](https://mobilerun.ai/blog/posts/droidrun-achieved-state-of-the-art-performance) - [Give OpenClaw access to mobile](https://mobilerun.ai/blog/posts/give-openclaw-access-to-mobile) - [How to automate apps with no API](https://mobilerun.ai/blog/posts/how-to-automate-apps-with-no-api) - [How to scrape data without getting banned](https://mobilerun.ai/blog/posts/how-to-scrape-data-without-getting-banned) - [Mobile AI agents](https://mobilerun.ai/blog/posts/mobile-ai-agents) - [mobilerun cloud phones](https://mobilerun.ai/blog/posts/mobilerun-cloud-phones) - [mobilerun vs GeeLark](https://mobilerun.ai/blog/posts/mobilerun-vs-geelark) - [Tasker vs mobilerun](https://mobilerun.ai/blog/posts/tasker-vs-mobilerun) - [Telegram automation beyond the bot API](https://mobilerun.ai/blog/posts/telegram-automation-beyond-the-bot-api) - [The phone farm is dead](https://mobilerun.ai/blog/posts/the-phone-farm-is-dead) - [The stealthness of AI agents](https://mobilerun.ai/blog/posts/the-stealthness-of-ai-agents) - [Turn old Android phones into AI agents](https://mobilerun.ai/blog/posts/turn-old-android-phones-into-ai-agents) - [Unlocking mobile apps for AI](https://mobilerun.ai/blog/posts/unlocking-mobile-apps-for-ai) - [We raised €2.1M to unlock mobile for AI](https://mobilerun.ai/blog/posts/we-raised-21m-to-unlock-mobile-for-ai) - [WhatsApp automation real number europe](https://mobilerun.ai/blog/posts/whatsapp-automation-real-number-europe) ## Developer resources - [Documentation](https://docs.mobilerun.ai): guides, API reference, quickstart - [API reference](https://docs.mobilerun.ai/api-reference): 90+ REST endpoints - [Python SDK](https://pypi.org/project/mobilerun-sdk/): pip install mobilerun-sdk - [TypeScript SDK](https://www.npmjs.com/package/@mobilerun/sdk): npm install @mobilerun/sdk - [MCP server](https://www.npmjs.com/package/@mobilerun/sdk-mcp): npm install @mobilerun/sdk-mcp, for Claude Code, Cursor, VS Code - [Framework source](https://github.com/droidrun/mobilerun): MIT licensed, the open-source engine - [Dashboard](https://cloud.mobilerun.ai): sign up, API keys, billing - [Blog](https://mobilerun.ai/blog): guides and comparisons - [Changelog](https://mobilerun.ai/changelog): what shipped, week by week - [Status page](https://status.mobilerun.ai): live uptime for Tasks API, Devices API, Cloud and VA --- # Solutions --- title: "mobilerun for AI agent builders · give your agent a real phone" description: "Give every user an AI agent on a real phone with real device and agent identity. Mobile automation across Android and iOS via REST, Python, TypeScript or MCP." url: "https://mobilerun.ai/solutions/ai-agent-builders" group: "Built for" --- # Your agent can think. Now it can tap. Your agent already has an email, a browser and a desktop. The missing piece is a real phone. It installs apps, taps and types across Android and iOS, from one task to a fleet. ## Why agents stay stuck in chat. - **Apps have no API**: The job lives inside an app. No endpoint, no webhook, just a screen. - **Emulators get refused**: Banking, rideshare and social apps run integrity checks. Emulators fail the checks real apps run, then quit. - **One phone is not a fleet**: A phone on your desk runs one task. Production needs an API and a fleet. ## The one missing piece: a real phone. What a headless browser is to web agents, mobilerun is to mobile agents. Give your agent the whole device on one API, with genuine hardware identity. - Any model, any framework. Claude, GPT, Gemini or open source, over REST, Python, TypeScript or MCP. - Android and iOS, the whole device. Real hardware, real device and agent identity that passes the checks real apps run. - Reads the accessibility tree, not just pixels. Fewer tokens and cleaner steps than vision-only agents. ## What your agent can run. - **Mobile RPA across apps**: Drive any app on Android or iOS. Tap, type, read, repeat. - **Run a personal assistant**: WhatsApp, Gmail, calendar and maps on one number, all day. - **Receive SMS and OTP**: A real number receives the code. Sign-ups and 2FA go through. - **Wire into your pipeline**: Trigger by API, stream the steps, get JSON back on a webhook. ## Example tasks - install my app fresh, walk through onboarding, confirm the home screen loads - open Gmail, find the latest invoice email, mark it important, archive it - clock in on my field app and export this week's attendance as JSON - in WhatsApp view recent chats, send a quick reply, attach a photo from the gallery --- Source: https://mobilerun.ai/solutions/ai-agent-builders --- title: "Enterprise mobile RPA across business units · mobilerun" description: "Automate mobile-first processes across your business. Citizen automation by chat, audit trails and a REST API over legacy and SAP apps, no backend change." url: "https://mobilerun.ai/solutions/enterprise-rpa" group: "Built for" --- # RPA for the apps your team taps. Automate the mobile-first processes that run in apps, not the ERP. An agent drives the apps your field and in-store teams already use, from a real phone, with no backend change. ## Why process automation stalls. - **The backend is off-limits**: Touching SAP or the ERP takes quarters. The process runs in apps today. - **Every unit works differently**: Wholesale, distribution and each division run their own apps and steps. One tool never fits all. - **The work is on the floor**: Field sales and in-store teams live in mobile apps, not on desktops. ## Mobile RPA on a real phone, no backend change. The agent operates the apps your teams already use from a real phone, so you automate the process without touching SAP, the ERP or the app vendor. Each business unit builds and owns its own agents. - Real hardware, real device and agent identity, recognized as a genuine device, so the apps your teams run see a genuine device and every run lands reliably. - Reads the accessibility tree, not just pixels, so runs are cheaper and more reliable than vision-only agents. - Citizen automation by chat, with an audit trail and human-in-the-loop on every sensitive step. ## What enterprises run. - **Automate field and in-store work**: The apps reps and store teams tap all day, end to end. - **Orchestrate across divisions**: One agent spans the apps each unit runs. - **Build an internal knowledge base**: Pull training docs and courses into a base your team can ask like chat. - **Keep humans in the loop**: Pause for approval on anything sensitive, logged. ## Example tasks - clock in on the field app and export today's attendance stats as JSON - pull this week's orders from the field app and flag the delayed ones - open the warehouse app, count low-stock items, and export a reorder list - sync the delivery app, confirm completed stops, and log exceptions as JSON --- Source: https://mobilerun.ai/solutions/enterprise-rpa --- title: "Social media automation on real phones · mobilerun" description: "Run your own and clients' authorized accounts on real phones with authentic device identity. One account per phone. Schedule, engage and report per client." url: "https://mobilerun.ai/solutions/social-media-automation" group: "Built for" --- # Every account on its own real phone. Run your own and your clients' authorized Instagram, TikTok and YouTube accounts on dedicated real phones, each with its own eSIM. One account per phone, for reliable delivery. ## Why running accounts at scale is hard. - **One device behind many accounts**: Stacking client accounts on one browser or phone blurs every identity. Reach and delivery suffer. - **Schedulers stop at posting**: Native tools publish on a clock, then leave replies, DMs and reporting to a person. - **Manual setups do not scale**: Buying, configuring and maintaining a phone per client stalls past a handful of accounts. ## One real phone per account. Give each authorized account its own real phone and eSIM. Real hardware, real device and agent identity, reliable delivery, and an agent that runs the day the way a person would. - Real hardware, real device and agent identity that passes the checks real apps run, because it is a real device. One account per phone, for reliable delivery and platform trust. - Publish on a schedule, engage the community, report per client. From the real apps. - Reads the accessibility tree, not just pixels. Up to 90% cheaper than vision-only agents. ## What social teams run. - **Publish on a schedule**: Queue reels, posts and stories, published on a clock per account. - **Engage and respond**: Comments and DMs drafted and triaged. A person approves before it sends. - **Onboard a new account**: A new authorized account on its own real phone and number, set up cleanly from day one. - **Report per client**: Pull reach, engagement and growth into a report per client. ## Example tasks - log into our brand Instagram, publish the queued reel, and confirm it posted - open our brand inbox on X, draft replies to new mentions, and pause for my approval - pull this week's post metrics from our TikTok account and export as JSON - check comments on our latest LinkedIn post and flag any needing a human reply --- Source: https://mobilerun.ai/solutions/social-media-automation --- title: "Sales and outreach automation on real phones · mobilerun" description: "Run LinkedIn, WhatsApp and SMS outreach from the mobile apps on real phones. Real hardware, real device and agent identity, one clean identity and a real number per rep, scaled by API." url: "https://mobilerun.ai/solutions/sales-outreach" group: "Built for" --- # SDR agents with real phones. Give every SDR agent a real phone on real hardware, with real device and agent identity. Run LinkedIn, WhatsApp and SMS outreach from the apps themselves, one clean identity and a real number per rep, driven by API. ## Why outreach gets blocked. - **LinkedIn checkpoints bots**: Browser plugins get blocked fast. The mobile app is the trusted surface. - **Headcount caps output**: Lists grow, reps do not. The repetitive part is agent work. - **Chat has no send API**: Personal WhatsApp and SMS outreach only happen on a device. ## Every agent gets its own real phone. Each agent runs on its own real phone: Real hardware, real device and agent identity, its own number, IP and city. It runs the apps your agent needs, so outreach is delivered and accounts stay legitimate. Your code drives them all. - Real hardware, real device and agent identity. Each real phone passes the checks real apps run. - One clean identity per rep. Number, IP and GPS stay separate, and human-paced typing with the daily caps you set keeps accounts healthy. - A real eSIM number for WhatsApp and SMS. Take the screen live to close. ## What sales teams run. - **Prospect on LinkedIn**: Visit, connect and message at a human pace. - **Run follow-up cadences**: Multi-day steps that stop the second a prospect replies. - **Move to WhatsApp**: Warm threads shift to a number that stays the same. - **Sync to your CRM**: Replies and outcomes post to HubSpot or Salesforce by webhook. ## Example tasks - Open LinkedIn, send my drafted intro to each accepted connection request - Reply to unread WhatsApp threads from my leads and log each response - Send the follow-up SMS to every prospect who opened yesterday's message - Pull new LinkedIn replies into a JSON list with contact and status --- Source: https://mobilerun.ai/solutions/sales-outreach --- title: "Procurement automation for mobile-only portals · mobilerun" description: "Supplier apps and vendor portals with no web and no API. Agents search, negotiate and order at scale, with structured JSON or CSV output." url: "https://mobilerun.ai/solutions/procurement" group: "Industry" --- # An API for mobile-only portals. Supplier apps and vendor portals with no web version and no API. Agents run on real phones that read as a normal user's device, then return structured data on a schedule. ## Why sourcing stays manual. - **The portal is the app**: Quotes and order status live in apps with no web and no API. - **Sourcing by thumb**: Every search, message and counter-offer is a person tapping. - **Scripts snap, agents drift**: Pure scripts break on updates. Pure agents cost too much per run. ## Vendor apps become reliable automation. Scripted steps where the app is stable, agent reasoning where it is not, all on real phones with genuine hardware identity. Supplier apps see a normal user's phone, and output lands in your stack. - Set up once, then re-run for a few cents. - Real phones pass the checks real apps run. - Webhook on done, into your ERP or n8n. Logins persist. ## What procurement runs. - **Search suppliers**: By spec, shortlisted with price and minimum order. - **Negotiate and quote**: Agents message many suppliers and counter on price, terms and lead time. - **Track orders**: Scheduled status checks, alerts on any change. - **Pull the data**: Prices and listings out as JSON or CSV. ## Example tasks - open Alibaba, search for LED panels, message the top suppliers for quotes and MOQ - read the supplier inbox and extract every quote, MOQ and lead time as JSON - reply to each supplier with a counter at my target price and log replies - reorder last month's SKUs in the vendor portal and return the order total as JSON --- Source: https://mobilerun.ai/solutions/procurement --- title: "Mobile EHR automation · mobilerun for healthcare" description: "Move clinical notes from scribe apps into the mobile EHR, field by field. Dedicated real phones, per-clinic templates, US data residency." url: "https://mobilerun.ai/solutions/healthcare" group: "Industry" --- # Mobile EHR, automated. Move clinical notes from the scribe app into the right patient chart in the mobile EHR. Each clinic runs on a dedicated real phone with full real-device identity, configured to its templates. ## Why EHR entry eats clinic time. - **Notes get typed twice**: The scribe captures the visit. A person re-types it into the chart. - **EHR apps have no API**: The mobile chart is a screen, not an endpoint. - **PHI raises the bar**: Patient data needs a dedicated real phone and an audit trail. ## From scribe to chart. An agent on a dedicated real phone types the note into the right patient record, field by field, the way a clinician would. Full real-device identity means the EHR app trusts it like any clinician's phone. - Real hardware, real device and agent identity: the real phone passes the checks real apps run, so the EHR app runs and stays logged in. - Patient matched on name, date of birth and record number first. - Flows pause for clinician unlock. A person stays in the loop. ## What clinics automate. - **Move signed notes**: From the scribe app into the right patient chart. - **Match the patient**: Verify name, date of birth and record number before any write. - **Map the template**: Per-clinic field layout, configured once. - **Sync data back**: Pull labs and vitals into your analytics. ## Example tasks - open the visit schedule, accept the pending visit, and sync the EHR app - fill in each note section in the mobile EHR, return status as JSON - pull today's completed visits and flag any with missing notes - walk the new-patient intake form and log every required field --- Source: https://mobilerun.ai/solutions/healthcare --- title: "Commerce QA and monitoring at fleet scale · mobilerun" description: "QA your storefront on real phones with authentic device identity: checkout and payment QA, price and stock monitoring, funnel audits and marketplace ops." url: "https://mobilerun.ai/solutions/commerce-automation" group: "Industry" --- # Your storefront, tested on real phones. Price and stock monitoring across markets, checkout QA and funnel audits on real phones with a genuine hardware fingerprint. Spin up a fleet in minutes, pin each device to a region. ## Why storefront QA can't keep up. - **Bugs hide until checkout**: Payment sheets, wallets and regional flows break in ways an emulator never shows. - **Prices drift per market**: Catalog and promo prices vary by country, app and store. Spot checks miss it. - **One phone can't cover it**: Every market, device and payment path is a person tapping through by hand. ## A real phone fleet for QA. Real phones on real hardware, with real device and agent identity that spin up in minutes, reset by API and report back per device. - 1 to 10,000 real phones running checkout QA in parallel. - Reset, install and run as one API loop. Pin each device to a market. - Real hardware, real device and agent identity that passes the checks real apps run. Flows behave the way customers see them. ## What commerce teams run. - **QA checkout in parallel**: Every payment path, across markets and devices, at once. - **Monitor price and stock**: Scheduled checks per market, alerts by webhook. - **Audit the funnel**: Walk the flow for UX regressions and dark patterns, screenshot each step. - **Operate your listings**: Update and verify your own marketplace listings at fleet scale. ## Example tasks - Walk my store checkout, list every payment option, flag any pre-checked upsell - Monitor price and stock on my product pages and diff vs yesterday - Fresh install my shopping app, sign up, verify by SMS, assert home loads - Add an item to cart, apply a coupon, confirm the discounted total --- Source: https://mobilerun.ai/solutions/commerce-automation --- title: "Event app lead generation · mobilerun" description: "Conference apps are mobile-only. The agent maps the app once and writes a reusable script. Re-runs are scripted, deterministic, and export clean CSV." url: "https://mobilerun.ai/solutions/event-lead-generation" group: "Built for" --- # The attendee list, extracted. Conference apps are mobile-only with no export. A real phone signs in with your ticket, walks the app once and writes a reusable script. After that, re-runs cost almost nothing. ## Why event leads stay locked up. - **The last mile is mobile**: Web covers most, but the event app has no export. - **Long lists break scrapers**: 3,000+ attendees overflow context windows and brittle scripts. - **Logins gate the list**: OTP codes and magic links stop bots at the door. ## Explore once, then script. A real phone signs in with your ticket, its real hardware, real device and agent identity recognized as genuine. The agent maps the app once and writes a reusable JSON script, so re-runs are scripted, deterministic and need no model. - Agent explores once. The script it writes re-runs with no LLM cost. - Holds 3,000 to 5,000 entries without losing place or looping. - Web or app, one real phone. Chrome handles event sites and directories. ## What agencies run. - **Map the app once**: The agent walks it and writes a reusable extraction script. - **Re-run on a schedule**: Scripted crawls, cron'd, no model per run. - **Pass the login**: Ticket plus OTP or magic link, on a real phone you control. - **Export to your CRM**: Clean CSV by webhook into enrichment and scoring. ## Example tasks - Open our booth's Whova event app, pull every scanned lead into a CSV - In Cvent, export the attendee list from our session as structured JSON - Open Eventbrite, list our order's registered attendees with company and title - Sync our Bizzabo scans, dedupe, and export name and company as CSV --- Source: https://mobilerun.ai/solutions/event-lead-generation --- title: "Mobile security testing on real phones · mobilerun" description: "Pentest your own mobile apps on real phones with full root, system-wide Frida, custom CA install and MITM. Dedicated isolated nodes for full control." url: "https://mobilerun.ai/solutions/security-testing" group: "Industry" --- # Pentest apps on real phones. Real phones with full root, system-wide Frida and custom CA install on a dedicated, isolated node. The agent walks every screen of your own app while your proxy logs the traffic. ## Why mobile pentests stall. - **Root detection blocks the rig**: Banking and fintech apps refuse a rooted emulator. - **Coverage is manual**: Someone taps every screen while the proxy records. - **OTP walls stop the scan**: Auth needs a real code, or half the surface stays dark. ## Real phones, built for AppSec. Real phones with genuine device identity, so your target app launches and behaves the way it does on a user's phone, with the root, instrumentation and isolation AppSec work needs. You drive the reversing yourself. - Full root and ADB. System-wide Frida, preinstalled. - Install custom CAs for MITM. Bring Burp or mitmproxy. - Real phones on genuine Android, not an emulator, so apps that refuse emulators still run. Your dedicated, isolated node stays yours. ## What security teams run. - **Enumerate the surface**: The agent walks the app, your proxy captures every request. - **Instrument with Frida**: System-wide Frida and full root, ready for your scripts. - **Capture traffic**: Install a custom CA, route through Burp or mitmproxy. - **Reverse on your own**: Full root and ADB. Drive the reversing yourself. ## Example tasks - install our staging APK, walk every screen, and log all GET and POST endpoints - open our app, capture every network request, and flag any plaintext HTTP traffic - walk our signup and checkout flows, log each endpoint and response code as JSON - install the debug build, tap through every screen, and list all third-party domains contacted --- Source: https://mobilerun.ai/solutions/security-testing --- title: "Game testing and agent evaluation on real phones · mobilerun" description: "Test game builds on real phones with genuine hardware identity across Android and iOS, evaluate game-playing agents, and capture gameplay for training data." url: "https://mobilerun.ai/solutions/gaming" group: "Industry" --- # Game QA and agents, on real phones. Test builds on real phones with authentic device identity across Android and iOS, evaluate game-playing agents, and capture gameplay for training. Rent the fleet, no hardware to buy or babysit. ## Why device coverage is the bottleneck. - **Hardware is a second job**: Racks, cables, resets and OS updates you never set out to run. - **Emulators are not the target**: Games behave differently on a real phone with authentic device identity, and integrity checks refuse an emulator outright. - **Coverage spans regions**: Every build needs many devices, OS versions and regional stores. ## Rent the fleet, keep the agents. Real phones with a genuine hardware fingerprint across Android and iOS, scaled on demand. You bring the build and the agents. We keep the phones online. - Reads the accessibility tree, not just pixels. Up to 90% cheaper than vision-only agents. - One phone to a fleet across OS versions and regional stores. Real hardware, real device and agent identity that passes the checks real apps run. - Sharp frames paired with action logs. Training data captured at scale. ## What gaming teams run. - **Evaluate game agents**: Run agent sessions on real phones and score every run. - **QA a build at scale**: One build across many devices, OS versions and regional variants. - **Capture training data**: Sharp frames paired with action logs for reinforcement learning. - **Cover every market**: Regional store and real latency, per device. ## Example tasks - install our latest game build, complete the tutorial, and assert level one loads - play 20 rounds of our puzzle game and log each score and move as JSON - walk every menu in our game build and capture each tap and screenshot as JSON - open our in-game store, list every coin pack, and flag any pre-checked purchase --- Source: https://mobilerun.ai/solutions/gaming --- title: "Mobile infrastructure for stealth-browser platforms · mobilerun" description: "Add a real mobile layer to your stealth browsers: genuine mobile device profiles and carrier-grade mobile IPs, delivered as infrastructure. Mobile-only." url: "https://mobilerun.ai/solutions/stealth-browser" group: "Industry" --- # A mobile layer for stealth browsers. Stealth-browser platforms run on desktop fingerprints. mobilerun adds the mobile layer: genuine mobile device profiles and carrier-grade mobile IPs, through one API. ## Where desktop stealth ends. - **Desktop fingerprints only**: Hosted browsers present a desktop profile. Mobile sites and checks expect a mobile device. - **The web is mobile-first**: More targets serve their primary, or only complete, experience to mobile clients. - **Mobile is hard to operate**: Real devices, carrier connectivity and device profiles are a logistics problem, not a software one. ## Mobile profiles, as infrastructure. mobilerun runs real and hosted Android phones behind one API, with genuine mobile device profiles and carrier-grade IPs. Extend your platform to mobile without operating a device fleet. - Genuine mobile device profiles your desktop stack does not produce. - Carrier-grade mobile IPs on real devices. - Mobile-only by design. We complement browser platforms, not compete with them. ## What you add to your platform. - **Real mobile device profiles**: Genuine mobile fingerprints your desktop infrastructure does not produce. - **Carrier-grade mobile IPs**: Route through real mobile carrier networks, not datacenter ranges. - **Real and hosted Android phones**: Provision real or virtual devices on demand, through one API. - **One API, your handoff**: Consumed through the developer handoff your platform already uses. ## Example tasks - Open a mobile browser and search for a laptop stand - Load a web page in the browser and capture a screenshot - Sign into a web app in the browser and confirm the dashboard loads - Fill a signup form in the browser and verify submission succeeds --- Source: https://mobilerun.ai/solutions/stealth-browser --- title: "Synthetic-user app testing on real phones · mobilerun" description: "AI agents run end-to-end UX tests on real phones on real hardware, with real device and agent identity, plus emulators. Minute-billed runs, recordings posted to CI." url: "https://mobilerun.ai/solutions/app-testing" group: "Built for" --- # Synthetic users on real phones. AI agents exercise your app like real users, on real phones with genuine hardware identity plus emulators. Describe the journey in plain language, get pass or fail with a recorded CI session. ## Why mobile QA stays painful. - **Scripts break on release**: A renamed id or a moved button kills the whole selector suite. - **Real journeys cross apps**: Signup spans Gmail, an SMS code and your app. - **Simulators hide bugs**: OEM skins and regional builds behave nothing like a clean simulator. ## A synthetic user on a real phone. The agent reads the screen and acts on intent, the way a person would, on a real phone with authentic device identity. Write the test in plain language and a renamed id is a non-event. - Plain-language tests that survive a renamed id. The agent finds the element by intent, not by selector. - Real phones and emulators, concurrent. Ephemeral runs of 5 to 30 minutes, billed by the minute. - Real hardware, real device and agent identity that passes the checks real apps run. Cross-app signup with real SMS and OTP, push checks, recorded session and screenshots posted to CI. ## What QA teams run. - **Test UX as a persona**: A synthetic user runs the whole journey and flags what confused it. - **Sign up across apps**: Real signup through Gmail, an SMS code and your screens. - **Test push notifications**: Trigger a push, tap it, assert the app opens to the right screen. - **Run nightly regression**: Scheduled journeys on real phones post pass or fail to CI. ## Example tasks - Fresh install Instagram, sign up, verify by SMS, assert the home feed loads. - Log in to Gmail, search a sender, mark important, archive the reply. - Walk the DoorDash checkout, list every payment option, flag any pre-checked upsell. - Play a show on Netflix, enable subtitles, and add it to My List. --- Source: https://mobilerun.ai/solutions/app-testing --- title: "Competitor app and pricing monitoring · mobilerun" description: "Watch competitor apps, pricing and features per market. Map each app once, then run scripted crawls on real phones that diff changes with an AI summary." url: "https://mobilerun.ai/solutions/market-intelligence" group: "Built for" --- # Watch every app that matters. Telecoms and enterprises track competitor apps and pricing per market. The agent maps each surface once, then scripted re-runs on a real phone report exactly what changed. ## Why app changes slip past. - **Moves ship in-app first**: New prices and plans appear in the app before any release note. - **Manual checks lapse**: Screenshots on a spare phone leave no history and miss a week. - **Web tools stop at the listing**: What changed inside the app, per market, stays invisible. ## Explore once, then crawl. The agent maps the app once and writes the crawl. After that, scripted re-runs on a real phone see exactly what each market's users see, and cost no LLM. The phone runs the apps your agent needs, so every competitor app renders the way its real users get it. - The agent maps it once. Scripted re-runs are deterministic and cost no LLM. - Real phones with a genuine hardware fingerprint that pass the checks real apps run and read as a normal user's phone, so every app renders like the live one. Screenshot diffs with an AI summary. - Per-market IP and GPS. See the prices and features each market actually gets. ## What intel teams track. - **Map the app once**: The agent walks the set screens and writes the crawl. - **Crawl every market**: Scripted re-runs on a real phone, weekly or daily. - **Diff the changes**: Compare to the last run, summarize what moved with AI. - **Deliver the brief**: Summary to Slack, data by webhook or n8n. ## Example tasks - open the competitor app on the US and German stores, capture pricing, diff vs last run - check Google Play top charts in Brazil and India, log each app's rank and rating - walk the competitor app, list every plan tier and price per market - open the shopping app, track a product's price and stock across two markets --- Source: https://mobilerun.ai/solutions/market-intelligence --- title: "mobilerun for white-label · stateful phones by the minute" description: "Give your platform a mobile layer with pay as you go, stateful on request. Devices per user, billed by the minute. Per-tenant metering and white-label." url: "https://mobilerun.ai/solutions/white-label" group: "Built for" --- # Spin up phones. Ship them as your own. Give your users a real mobile environment behind one API, branded as your product. Pay only while a device runs, and its logins and state persist. No monthly rent per phone. ## Why renting phones by the month bleeds. - **The phone is missing**: Your users' agents already have email, a browser and a desktop. Not a phone. - **Monthly rent bleeds on idle**: Subscription phones bill every day to stay alive, even while your users' devices sit unused between sessions. - **No way to rebill**: You can't meter usage per end-user, so billing your own customers is a guess. ## Stateful phones, by the minute. Your product and your customer on top, our phones underneath. Spin a device up when a user needs it, pay only while it runs, then spin it down. State persists, so the next session resumes with no idle rent and no re-setup. - Pay as you go, stateful on request. Pay by the minute while a device runs, nothing when it is down. No monthly rent per phone. - State persists between sessions. Logins, app state and identity resume, so nothing is set up twice. - Per-tenant metering, team accounts and full white-label. Rebill your users under your own brand. ## What you ship on top. - **Spin up on demand**: Provision a real phone the moment a user needs one, release it when they are done. - **Resume without re-setup**: State persists between sessions, so a returning user picks up logged in, at no idle cost. - **Meter and rebill by tenant**: Per-tenant usage lands in your billing. Mark it up, invoice your way. - **Ship it white-label**: Your name, your UX, your docs. Your customers never see mobilerun. --- Source: https://mobilerun.ai/solutions/white-label --- # Per-app guides --- title: "Google Search Agent · deploy on a real phone | mobilerun" description: "Research, compare and monitor live search results from a configured country or region. Deploy the agent on persistent Android or iOS with Connect, eSIM and observability through mobilerun." url: "https://mobilerun.ai/apps/google-search" category: "Work" --- # Deploy a Google Search Agent on a real phone. Research, compare and monitor live search results from a configured country or region. It works inside the app on a persistent phone and returns the result with screenshots and a complete step trajectory. ## What the Google Search Agent does - **Research a market**: Run the same question from selected regions and return the sources and visible results. - **Monitor results**: Repeat a search on a schedule and report what appeared, moved or disappeared. - **Hand off to an app**: Find the result in Search, then continue the task inside the native app on the same phone. ## One agent, the whole phone stack The agent, device, network route, number and observability live in one platform. Configure the phone for any region, keep the signed-in state, and run it by API, SDK, MCP or the Assistant. - Persistent Android and iOS. Keep app state between runs instead of signing in again. - mobilerun Connect and eSIM. Match the network and number to the task without stitching providers together. - Live view and trajectory. See screenshots, actions and structured output for every run. ## Example tasks - Research a market - Monitor results - Hand off to an app ## FAQ **What is a Google Search Agent?** A mobilerun agent that works inside Google Search on a persistent Android or iOS phone. Give it a task in plain language or call it through the API, SDK or MCP. **Can I choose the country or region?** Yes. Configure the device GPS, locale, language and timezone for any region, then select the Connect route separately. **Can I see what the agent did?** Yes. Watch the phone live and inspect the screenshots, actions, trajectory and structured result after the run. --- Source: https://mobilerun.ai/apps/google-search --- title: "Messenger Agent · deploy on a real phone | mobilerun" description: "Triage conversations, prepare replies and handle approved customer messages from your account. Deploy the agent on persistent Android or iOS with Connect, eSIM and observability through mobilerun." url: "https://mobilerun.ai/apps/messenger" category: "Messaging" --- # Deploy a Messenger Agent on a real phone. Triage conversations, prepare replies and handle approved customer messages from your account. It works inside the app on a persistent phone and returns the result with screenshots and a complete step trajectory. ## What the Messenger Agent does - **Triage the inbox**: Read new conversations and separate questions, orders and issues into a clean queue. - **Prepare replies**: Draft a response in your voice and hold sensitive messages for approval. - **Follow up**: Check conversations that need a response and continue from the existing thread. ## One agent, the whole phone stack The agent, device, network route, number and observability live in one platform. Configure the phone for any region, keep the signed-in state, and run it by API, SDK, MCP or the Assistant. - Persistent Android and iOS. Keep app state between runs instead of signing in again. - mobilerun Connect and eSIM. Match the network and number to the task without stitching providers together. - Live view and trajectory. See screenshots, actions and structured output for every run. ## Example tasks - Triage the inbox - Prepare replies - Follow up ## FAQ **What is a Messenger Agent?** A mobilerun agent that works inside Messenger on a persistent Android or iOS phone. Give it a task in plain language or call it through the API, SDK or MCP. **Can I choose the country or region?** Yes. Configure the device GPS, locale, language and timezone for any region, then select the Connect route separately. **Can I see what the agent did?** Yes. Watch the phone live and inspect the screenshots, actions, trajectory and structured result after the run. --- Source: https://mobilerun.ai/apps/messenger --- title: "Meta Business Suite Agent · deploy on a real phone | mobilerun" description: "Manage posts, comments, messages and performance across your connected Facebook and Instagram presence. Deploy the agent on persistent Android or iOS with Connect, eSIM and observability through mobilerun." url: "https://mobilerun.ai/apps/meta-business-suite" category: "Social" --- # Deploy a Meta Business Suite Agent on a real phone. Manage posts, comments, messages and performance across your connected Facebook and Instagram presence. It works inside the app on a persistent phone and returns the result with screenshots and a complete step trajectory. ## What the Meta Business Suite Agent does - **Publish across channels**: Prepare and publish approved content to connected Facebook and Instagram accounts. - **Work the unified inbox**: Triage comments and messages from one place and prepare replies. - **Pull the daily report**: Collect the visible performance numbers and return a structured recap. ## One agent, the whole phone stack The agent, device, network route, number and observability live in one platform. Configure the phone for any region, keep the signed-in state, and run it by API, SDK, MCP or the Assistant. - Persistent Android and iOS. Keep app state between runs instead of signing in again. - mobilerun Connect and eSIM. Match the network and number to the task without stitching providers together. - Live view and trajectory. See screenshots, actions and structured output for every run. ## Example tasks - Publish across channels - Work the unified inbox - Pull the daily report ## FAQ **What is a Meta Business Suite Agent?** A mobilerun agent that works inside Meta Business Suite on a persistent Android or iOS phone. Give it a task in plain language or call it through the API, SDK or MCP. **Can I choose the country or region?** Yes. Configure the device GPS, locale, language and timezone for any region, then select the Connect route separately. **Can I see what the agent did?** Yes. Watch the phone live and inspect the screenshots, actions, trajectory and structured result after the run. --- Source: https://mobilerun.ai/apps/meta-business-suite --- title: "Banking Agent · deploy on a real phone | mobilerun" description: "Read balances, prepare payments and complete approved tasks inside your banking apps. Deploy the agent on persistent Android or iOS with Connect, eSIM and observability through mobilerun." url: "https://mobilerun.ai/apps/banking" category: "Work" --- # Deploy a Banking Agent on a real phone. Read balances, prepare payments and complete approved tasks inside your banking apps. It works inside the app on a persistent phone and returns the result with screenshots and a complete step trajectory. ## What the Banking Agent does - **Read and reconcile**: Collect balances and recent transactions, then return a structured summary. - **Prepare a payment**: Enter the payment details and pause for approval before the final confirmation. - **Handle one-time codes**: Receive the code on the same phone and continue the approved banking task. ## One agent, the whole phone stack The agent, device, network route, number and observability live in one platform. Configure the phone for any region, keep the signed-in state, and run it by API, SDK, MCP or the Assistant. - Persistent Android and iOS. Keep app state between runs instead of signing in again. - mobilerun Connect and eSIM. Match the network and number to the task without stitching providers together. - Live view and trajectory. See screenshots, actions and structured output for every run. ## Example tasks - Read and reconcile - Prepare a payment - Handle one-time codes ## FAQ **What is a Banking Agent?** A mobilerun agent that works inside Banking on a persistent Android or iOS phone. Give it a task in plain language or call it through the API, SDK or MCP. **Can I choose the country or region?** Yes. Configure the device GPS, locale, language and timezone for any region, then select the Connect route separately. **Can I see what the agent did?** Yes. Watch the phone live and inspect the screenshots, actions, trajectory and structured result after the run. --- Source: https://mobilerun.ai/apps/banking --- title: "Automate Discord with an AI agent · mobilerun" description: "Run and moderate your own Discord server with an AI agent on a real phone. Post updates, watch your channels, queue mod actions for approval. Pay as you go." url: "https://mobilerun.ai/apps/discord" category: "Messaging" --- # Run your Discord community on a real phone. Point an AI agent at a real Android or iOS phone to run your own server. It runs the apps your agent needs, so announcements and mod actions land. Authorized servers only. ## What the agent does on Discord - **Post updates to your server**: Schedule announcements, patch notes, and event reminders. The agent opens Discord and posts on your account, on time. - **Monitor channels you belong to**: Watch the servers and channels you belong to. The agent tracks keywords, mentions, and new threads, then hands you a digest. - **Support moderation with approval**: Flag spam, off-topic posts, and rule breaks. The agent queues each action and waits for your yes. You stay the moderator. ## Why a real phone works where scripts fail Discord runs on a phone, so your agent gets one. mobilerun drives the real Discord app on Android and iOS, on real hardware, with real device and agent identity recognized as genuine. It reads the screen like a person and keeps your session. - A real phone running the real Discord app on your own account keeps community work first-party and human-like, not a headless bot on an API. - Drive it with any model via API, SDK, MCP, or a chat VA. It reads the accessibility tree, not pixels, up to 90% cheaper than vision-only runs. - Sessions stay logged in and pay-as-you-go, so you keep state between tasks and pay only for the minutes you use. ## Example tasks - Open Discord, go to a server, and post a message in general - Search a channel for the keyword release and screenshot the top result - Accept a friend request, then open a direct message and reply - Set my status to Do Not Disturb and mute a busy channel ## FAQ **Can I automate Discord with an AI agent?** Yes. mobilerun runs the real Discord app on a real phone so an agent can post updates, monitor channels, and prepare mod actions. Keep to your own or authorized servers, routing decisions through your approval. **Why run on a real phone instead of a headless client?** A real phone passes the checks real apps run. Running the real Discord app on your own account keeps the work first-party and within Discord's terms. **Does the agent moderate on its own?** No. It flags spam, rule breaks, and off-topic posts and queues the action, but nothing runs until you approve it. You stay in control of every removal, warning, and mute. --- Source: https://mobilerun.ai/apps/discord --- title: "Automate Gmail with an AI agent · mobilerun" description: "Automate Gmail with an AI agent on a real phone. Triage your inbox, send and follow up, receive OTP codes, run e-sign flows. Gmail automation, hosted." url: "https://mobilerun.ai/apps/gmail" category: "Messaging" --- # Automate Gmail on a real phone. Your agent signs in to your own Gmail on a real Android or iOS phone with genuine hardware identity. It triages, sends, follows up, catches OTP codes, and runs e-sign flows. ## What agents do in Gmail. - **Triage the inbox**: Point your agent at your own Gmail to read, label, archive, and flag what needs a human, fast and cheap across your threads. - **Send and follow up**: Draft, send, and chase replies from your authorized account. Agent writes, waits for the reply, and follows up on schedule. - **Receive codes and sign**: Get your own OTP and 2FA codes on the device, then carry them into the flow that needs them. Run e-sign flows end to end. ## Why a real phone. Gmail was built for phones, not scripts. Your agent runs on a real Android or iOS device on real hardware, with real device and agent identity: it passes the checks real apps run. That legitimacy is why your mail sends, codes arrive, and sessions hold. - Authentic device identity. A real phone with a real number reads like an ordinary user's device, so your authorized mail stays deliverable. - Any model, any stack. Drive Gmail from the model you already use over API, SDK, or MCP, or hand it to a chat VA. - Cheaper by default. Your agent reads the accessibility tree, up to 90% cheaper than vision-only, and the real phone is pay as you go, stateful on request. ## Example tasks - Log into my Gmail, search for the receipt sender, mark it important, archive the reply - QA the Gmail login screen, enter credentials, assert the inbox loads - Open Gmail, compose a test email, attach a photo from the gallery, send it - Monitor my Gmail inbox for new order alerts and return each as JSON ## FAQ **Can I automate Gmail with an AI agent?** Yes. mobilerun runs your own Gmail on a real phone, and your AI agent drives it over API, SDK, or MCP. It can triage, send, follow up, and complete e-sign flows. **Will my mail stay deliverable?** Yes. Your account runs on a real phone that passes the checks real apps run. That's why your authorized, first-party mail sends and sessions stay trusted. **Can it receive OTP and 2FA codes?** Yes. Because your account lives on a real phone with a real number, your OTP and 2FA codes land on the device, and the agent can read and use them in the same run. --- Source: https://mobilerun.ai/apps/gmail --- title: "Automate Telegram with an AI agent · mobilerun" description: "Automate Telegram on a real phone with real-device identity. Monitor channels you follow, extract posts on a schedule, and run first-party messaging." url: "https://mobilerun.ai/apps/telegram" category: "Messaging" --- # Automate Telegram on a real phone. Your agent drives the real Telegram app on a real phone with genuine hardware identity. It monitors channels you follow, pulls new posts on a schedule, and runs your account. ## What agents do in Telegram. - **Monitor channels you follow**: Point your agent at the channels you follow. It opens each in the real app and reports what changed, so you skip the scroll. - **Extract new posts on a schedule**: Run a scheduled pass that pulls fresh posts since the last check and returns clean, structured text for digests and research. - **Set up and run your own account**: Register your number, complete OTP on-device, and message people who expect you. Real hardware, first-party from first tap. ## Why a real phone. Telegram is built for real people. A mobilerun real phone runs real Android and iOS, passes the checks real apps run. Drive it with a real number and setup, OTP, and messages deliver reliably. - Real hardware, real device and agent identity: a real number on a phone that passes the checks real apps run, so setup and first-party messages land reliably. - Any model, any way to call it: drive the real phone from your own agent over API, SDK, or MCP, or hand it to a chat VA. - Reads the accessibility tree, up to ~90% cheaper than vision-only, and runs pay as you go, stateful on request, so a monitor bills only while it works. ## Example tasks - Open Telegram, view recent chats, send a quick reply, and attach a photo - Open my Saved Messages, pin an important note, and confirm it stays on top - Scroll my own channel and export every new post since yesterday as JSON - Search my support chats, mark unread threads important, and summarize each one ## FAQ **Can I automate Telegram with an AI agent?** Yes. mobilerun runs the real Telegram app on a real phone your AI agent drives via API, SDK, or MCP. It monitors channels you follow, extracts new posts on a schedule, and sets up and runs your own account. **Does it read as a normal user's phone?** Yes. Each real phone passes the checks real apps run. It taps through the real app with a real number, and setup, OTP, and messages deliver as expected. **What Telegram tasks fit best?** Monitoring public channels you subscribe to, pulling new posts into structured text on a schedule, and running setup and messaging from your own account. It is built for first-party, ToS-clean automation. --- Source: https://mobilerun.ai/apps/telegram --- title: "Automate WhatsApp with an AI agent · mobilerun" description: "Automate WhatsApp with an AI agent on a real phone with real-device identity. Business messaging, confirmations, OTP and QA on a number you own." url: "https://mobilerun.ai/apps/whatsapp" category: "Messaging" --- # Automate WhatsApp on a real phone. Your agent runs WhatsApp on a real phone with a number you own. Genuine hardware identity means authorized messages deliver, orders get confirmed, and your own codes arrive. ## What agents do in WhatsApp. - **Authorized business messaging**: Reach customers who opted in. Send updates, reply to questions, and follow up from a number your team owns. - **Confirmations and codes**: Confirm orders, deliveries and bookings from a real number. Your own OTP and 2FA codes arrive, so accounts you own activate. - **QA WhatsApp Business flows**: Run signup and activation on a real device. See exactly what your users see, and catch what breaks before it ships. ## Why a real phone. WhatsApp lives on phones. mobilerun gives your agent a real phone and number on real hardware, with real device and agent identity, so it passes the checks real apps run. That's why authorized messages deliver. Drive it by API, SDK, MCP or a chat VA. - A real phone with a real number is a genuine first-party account, not an emulator profile, so your authorized messages deliver. - Drive it with any model over API, SDK or MCP, or hand tasks to a chat VA. - Your agent reads the accessibility tree, not just pixels. Up to 90% cheaper than vision-only. ## Example tasks - Log into my WhatsApp account, open recent chats, and send a quick reply - QA WhatsApp onboarding: fresh install, register by SMS, and assert the chat list loads - Monitor my own WhatsApp Business inbox and export every new customer message as JSON - Test a WhatsApp voice call to my test contact, mute, then end and log it ## FAQ **Can I automate WhatsApp with an AI agent?** Yes. Your agent runs the WhatsApp app on a real phone and drives it by API, SDK, MCP or a chat VA. It sends authorized messages, confirms orders, and receives your own codes. **Does it run as a genuine account?** Yes. It runs on a real phone that passes the checks real apps run, with a number you own. Built for authorized messaging and QA, not mass unsolicited sending. **What can I use it for?** Authorized business messaging, delivery and booking confirmations, receiving your own OTP, and QA of WhatsApp Business signup flows. Always on accounts you own or are cleared to run. --- Source: https://mobilerun.ai/apps/whatsapp --- title: "Automate Facebook with an AI agent · mobilerun" description: "Run Facebook on a real phone your AI agent drives. Manage your own Pages and Marketplace listings, draft buyer replies and monitor your presence." url: "https://mobilerun.ai/apps/facebook" category: "Social" --- # Automate Facebook on a real phone. mobilerun gives your agent a real phone signed into your own Facebook account. Genuine hardware identity is compatible with the checks real apps run, so first-party actions land. ## What agents do in Facebook. - **Manage your Pages and Marketplace**: Post updates, refresh your Marketplace listings, and keep prices and details current inside your authorized account. - **Reply to buyers and comments**: Read new Messenger threads and Page comments, then draft responses for you to approve before anything sends. - **Monitor your presence and mentions**: Track your Pages, listings, and mentions on a schedule, surfacing new buyer questions and activity so nothing slips past. ## Why a real phone works. Facebook is built for phones, so your agent runs on one. mobilerun hosts real Android and iOS phones signed into your own account, driven by any model. Each carries real hardware, real device and agent identity, is compatible with the checks real apps run, and stays pay as you go, stateful on request. - Real hardware, real numbers, a genuine device fingerprint, so your first-party actions land as legitimate and your buyer replies deliver. - Drive it with any model over API, SDK, or MCP, or hand tasks to a chat VA. Your stack, your choice of agent. - The agent reads the accessibility tree instead of screenshots, up to about 90% cheaper than vision-only, and just as reliable. ## Example tasks - log into our page, publish the scheduled post, and confirm it went live - open Marketplace, refresh my store listings, and answer new buyer messages - walk the login flow, then assert the news feed loads correctly - check our page inbox, draft replies to new comments, return them as JSON ## FAQ **Can I automate Facebook with an AI agent?** Yes. mobilerun runs Facebook on a real phone signed into your own account, and your agent drives it over API, SDK, or MCP. It manages your Pages and Marketplace and drafts replies for your approval. **Does real-device identity make my automation more legitimate?** Yes. Your agent works on a real phone, Android or iOS, with authentic device identity that passes the checks real apps run. It runs the apps your agent needs, so first-party actions land as legitimate. **Will the agent send messages without me?** No. For buyer replies and comments, the agent drafts responses and holds them for your approval. Nothing sends until you say so, so you control what goes out under your name. --- Source: https://mobilerun.ai/apps/facebook --- title: "Automate Instagram with an AI agent · mobilerun" description: "Automate Instagram on a real phone with real-device identity. An AI agent publishes, triages DMs and pulls analytics on your authorized accounts." url: "https://mobilerun.ai/apps/instagram" category: "Social" --- # Automate Instagram on a real phone. Your agent gets a real phone with authentic device identity, so Instagram reads it as a normal user's phone. It posts, triages DMs, and pulls analytics, human in the loop. ## What agents do in Instagram. - **Publish and schedule**: Draft, review, and publish posts, Reels, and Stories to owned or authorized accounts. What you approve is what goes live. - **Triage and answer DMs**: Read DMs, sort them by intent, and draft replies. Nothing sends without approval, so your voice stays in control. - **Pull analytics and QA flows**: Collect reach, engagement, and follower trends, and QA your publishing and messaging flows on real hardware first. ## Why a real phone. Instagram is built for a phone, so run it on a real phone in the cloud. Every device passes the checks real apps run, so your first-party activity reads as legitimate. That keeps posts, DMs, and delivery reliable. - Genuine hardware identity. Your real phone runs real Android and iOS with a real app build, so authorized activity looks like a person's device. - Any model, one interface. Point any LLM at the device over API, SDK, or MCP, or hand a task to the chat VA. - Reads the screen, not just pixels. Agent works from the accessibility tree, ~90% cheaper than vision-only, with pay as you go, stateful on request, on devices. ## Example tasks - log into our brand Instagram, publish the scheduled reel, and confirm it posts - open our Instagram business insights, screenshot reach and saves, export as JSON - review our Instagram Shop listings, update sold-out prices, and answer buyer DMs - fresh install Instagram, log into our account, and verify the home feed loads ## FAQ **Can I automate Instagram with an AI agent?** Yes. mobilerun gives your AI agent a real phone to drive Instagram over API, SDK, or MCP. It publishes, triages DMs, and pulls analytics on accounts you own or are authorized to manage. **Does it work like a normal user on Instagram?** Yes. Your real phone runs Android or iOS on real hardware, with real device and agent identity and passes the checks real apps run, so It is real hardware end to end. Approval stays human. **Do DM replies and posts go out automatically?** Only with your approval. The agent drafts replies and prepares posts, and a human signs off before anything is sent or published, so you keep control of voice and timing. --- Source: https://mobilerun.ai/apps/instagram --- title: "Automate Pinterest with an AI agent · mobilerun" description: "Drive the Pinterest app on real phones with an AI agent. Publish pins to your own boards, read your own analytics, and QA links and rich pins on real devices." url: "https://mobilerun.ai/apps/pinterest" category: "Social" --- # Run Pinterest on a real phone Give an AI agent a real phone that opens Pinterest and works your own authorized account. It runs the apps your agent needs, so first-party actions land on Android and iOS. ## What you can automate on Pinterest - **Publish pins to your own boards**: Point the agent at your authorized account to post pins, set titles and destination links, and file them to the right boards. - **Read your own analytics**: Pull the numbers from your own Pinterest analytics to see how pins and boards perform over time, no manual checking. - **QA the app on real devices**: Test pins, links, and rich content the way a customer sees them. Real Android and iOS phones surface issues emulators miss. ## Why a real phone beats a script Pinterest is built for a phone, so automate it on one. mobilerun runs your agent on real hardware, with real device and agent identity: it passes the checks real apps run, so first-party work on your own account is recognized as legitimate. - Genuine hardware identity. The agent works from a real phone that passes the checks real apps run, so it reads as a real user's. - Any model, any interface. Drive from any model via API, SDK, MCP, or a chat VA. It reads the accessibility tree, ~90% cheaper than vision-only. - Pay as you go, stateful on request. The session keeps state, so the agent resumes where it left off, and you pay only for the time you use. ## Example tasks - log into my Pinterest business account, create a board, and pin three product photos - open Pinterest, search my brand keyword, and save the top results to a board - check my Pinterest shop pins, refresh out-of-stock products, and reply to buyer comments - schedule my draft pins for the week and confirm they are published ## FAQ **Can I automate Pinterest with an AI agent?** Yes. mobilerun gives the agent a real phone that opens Pinterest and drives your own authorized account, all first-party: it publishes pins, organizes boards, and reads your own analytics. **Why does real-device identity matter?** Pinterest expects a real phone. mobilerun runs on genuine hardware that passes the checks real apps run, so it is real hardware end to end and legitimate actions land cleanly. **Which models and interfaces can drive it?** Any model you like, through API, SDK, or MCP, or a chat VA for hands-off tasks. The agent reads the accessibility tree, up to about 90% cheaper than vision-only. --- Source: https://mobilerun.ai/apps/pinterest --- title: "Automate Reddit with an AI agent · mobilerun" description: "Run the Reddit app on a real phone, real Android or iOS. Monitor subreddits, post and comment from your authorized account, and research public threads." url: "https://mobilerun.ai/apps/reddit" category: "Social" --- # Put Reddit on autopilot, on a real phone mobilerun gives your AI agent a real phone, Android or iOS, that drives the Reddit app directly. Genuine hardware identity means your account behaves as a normal user. ## What agents do on Reddit - **Monitor the subreddits you care about**: Track the communities and keywords you care about. Your agent scans new posts and comments, flagging what needs a human. - **Post and comment with human approval**: Draft replies and posts from your authorized account, then hold each one for your sign-off. Nothing goes live without you. - **Research public discussions on a schedule**: Pull public threads, top comments, and community sentiment on a schedule. Your agent hands you a clean summary to act on. ## Why mobilerun for Reddit Reddit runs on a phone. mobilerun gives your agent a real phone, Android and iOS, so the app behaves exactly as it does for any real user. Authentic device identity means your account behaves as a normal user's: legitimate first-party activity. - Real hardware, real device and agent identity. Your authorized account runs on a real phone recognized as genuine, so activity reads as legitimate. - Any model, your way. Drive the real phone through API, SDK, or MCP with whatever model you prefer, or hand a task to the chat VA. - Reads the accessibility tree, up to about 90% cheaper than vision-only runs, and you pay as you go, stateful on request. ## Example tasks - Log into the brand account, post the announcement to a subreddit, pin it - Monitor a subreddit, pull top new posts and overall sentiment as JSON - Reply to unanswered comments on the latest post from the brand account - QA the Reddit app: fresh install, sign in, load home feed, assert it renders ## FAQ **Can I automate Reddit with an AI agent?** Yes. mobilerun runs the Reddit app on a real phone, Android or iOS, driven by your agent via API, SDK, MCP, or chat VA. It monitors subreddits, drafts posts for approval, and researches threads on a schedule. **How does real-device identity help on Reddit?** Each mobilerun device is real hardware that passes the checks real apps run, so your authorized account is real hardware end to end. It's genuine first-party activity, never a way to hide who you are. **Do I stay in control of what gets posted?** Yes. Set the agent to hold every post and comment for human approval, so nothing goes public without your sign-off. Every action also lands in the audit log for you to review. --- Source: https://mobilerun.ai/apps/reddit --- title: "Automate Snapchat with an AI agent · mobilerun" description: "Drive Snapchat on mobilerun real phones with an AI agent. Publish Stories, monitor your own presence, and QA the app on real Android and iOS devices." url: "https://mobilerun.ai/apps/snapchat" category: "Social" --- # Automate Snapchat on a real phone Point an AI agent at your Snapchat, or a brand account you're authorized to manage. It runs on a real phone with real device and agent identity, posting Stories and QAing it. ## Real work on Snapchat, handled - **Publish Stories on schedule**: Hand over approved Stories and Spotlight posts. It posts them to your brand account on schedule, confirming each is live. - **Watch your own presence**: It opens your profile daily to check Story views, replies, and how posts render on a real screen, flagging anything off. - **QA the app on real devices**: Ship ad creative, deep links, or integrations. It walks your flows on real Android and iOS phones and reports what users see. ## Why it holds up on Snapchat Snapchat is built for phones, so mobilerun runs on real ones. A session is a real Android or iOS device driven like a person, on real hardware, with real device and agent identity that passes the checks real apps run. Your account reads as normal, Stories stay deliverable. - Genuine hardware identity. Each session is a real Android or iOS phone that runs the apps your agent needs, so Stories reach followers. - Any model, your way. Drive it over API, SDK, or MCP, or hand the task to a chat VA. Bring the model you already trust. - Cheaper to run, simple to bill. The accessibility tree costs up to 90% less than vision-only, on pay-as-you-go phones billed only while running. ## Example tasks - fresh install Snapchat, sign in, verify by SMS, and assert the camera screen loads - log into Snapchat, send a snap to a saved chat, and add it to my story - open Snapchat chats, send a quick reply, and attach a photo from the gallery - open my brand's Snapchat Public Profile and capture Spotlight and Story view stats as JSON ## FAQ **Can I automate Snapchat with an AI agent?** Yes. mobilerun gives an AI agent a real phone that opens Snapchat and taps through like a person. Point it at your account, or one you're authorized to manage, to post Stories, monitor presence, and QA the app. **Why run on a real phone instead of an emulator?** A mobilerun session is a real Android or iOS device with an authentic hardware fingerprint that passes the checks real apps run, so posts publish and Stories reach followers, unlike data-center setups. **Whose accounts can I automate?** Your own, or accounts you are authorized to manage for a client or brand. mobilerun is built for first-party, permission-based automation, not for creating throwaway accounts or working around Snapchat's rules. --- Source: https://mobilerun.ai/apps/snapchat --- title: "Automate TikTok with an AI agent · mobilerun" description: "Automate TikTok on a real phone. An AI agent publishes on a schedule, pulls analytics and QAs the app. TikTok automation for authorized accounts." url: "https://mobilerun.ai/apps/tiktok" category: "Social" --- # Automate TikTok on a real phone. Your agent runs TikTok on a real phone with real device and agent identity. It publishes on schedule, pulls analytics and QAs the app on authorized accounts. ## What agents do in TikTok. - **Publish on a schedule**: Queue videos, captions and hashtags. Your agent posts on time on accounts you're authorized to manage, human-approved. - **Pull performance analytics**: Read views, watch time and follower trends from the app. Your agent exports them to your dashboard on the cadence you set. - **QA on real devices**: Test your TikTok flows, uploads and playback on real Android and iOS. Catch broken posts, stuck renders and layout bugs. ## Why a real phone. TikTok is built for a phone, so your agent gets one in the cloud. Real hardware, not a spoof: it passes the checks real apps run, so your authorized account posts and loads analytics like any user. No emulator to get refused. - Real hardware, real device and agent identity. A real phone with a real number, the same setup a person uses. Your content ships and your data loads reliably. - Any model, any stack. Drive the phone from REST, Python, TypeScript or MCP. Point Claude, Gemini or your model at it, or hand it to a chat VA. - Reads the screen, not just pixels. Your agent works off the accessibility tree, up to 90% cheaper than vision-only. Pay as you go, stateful on request. ## Example tasks - Fresh install TikTok, sign up, verify by SMS, and assert the For You feed loads. - Open TikTok, watch the top videos, enable captions, and save one to favorites. - Log in to TikTok Shop, check my listings, and reply to pending buyer questions. - Search a topic on TikTok, watch the top videos, and follow one creator. ## FAQ **Can I automate TikTok with an AI agent?** Yes. Your agent drives TikTok on a real phone to publish on a schedule, pull analytics and QA the app. It runs on accounts you own or are authorized to manage, with a human in the loop. **Will posts and analytics work reliably?** Your agent runs on a real phone that passes the checks real apps run, so uploads publish and analytics load like a normal mobile session for your authorized accounts. **Which accounts can I run?** Only your own accounts, or client accounts you're authorized to manage. mobilerun is for legitimate, first-party automation and QA on accounts you control. --- Source: https://mobilerun.ai/apps/tiktok --- title: "Automate X with an AI agent · mobilerun" description: "Run X on real phones an AI agent drives. Schedule posts, monitor mentions, pull analytics, and QA the app on your authorized accounts." url: "https://mobilerun.ai/apps/x" category: "Social" --- # Drive X on a real phone Give an AI agent a real phone running X on Android or iOS, with a hardware fingerprint with real device and agent identity. Schedule posts, watch mentions, pull numbers, QA. ## What the agent does on X - **Publish on a schedule**: Queue posts for your own or a client's authorized account. The agent taps through the real X app at set times, like a person. - **Monitor mentions and keywords**: Point the agent at your handle, brand terms, or a hashtag. It watches the feed and digests replies worth a human's time. - **Pull your analytics**: The agent opens your analytics, reads impressions, engagement, and follower moves, exports on a cadence. No scraper guesses. ## Why a real phone beats a script X behaves like X only on a real device. mobilerun gives the agent a real Android or iOS phone on real hardware, with real device and agent identity, so it passes the checks real apps run. What you automate matches what a person sees, no emulator gaps. - Real hardware, not a spoof, so your authorized first-party automation reads as normal use. Posts, mentions, and analytics behave as they should. - Drive it with any model over API, SDK, or MCP, or hand tasks to a chat VA. It reads the accessibility tree, up to ~90% cheaper than vision-only. - Real phones are pay as you go, stateful on request. Keep a session signed in, pay for the minutes you use, and stop when you are done. ## Example tasks - log into our brand account on X, post the scheduled announcement, pin it - QA the X signup: fresh install, verify by SMS, assert home feed loads - monitor our support mentions on X and export new ones as JSON - reply to authorized DMs on X, then log each handled thread as JSON ## FAQ **Can I automate X with an AI agent?** Yes. mobilerun runs the real X app on a real phone an AI agent drives via API, SDK, MCP, or a chat VA. It works on your own or clients' authorized accounts, with a human in the loop for anything public. **Why does a real device matter for X?** X is built for phones, so it behaves most like itself on a real device. mobilerun's phones pass the checks real apps run, so your authorized automation reads as normal use and posts what a person would. **What can I safely automate?** Publishing on a schedule, monitoring mentions and keywords, pulling your own analytics, and QA testing the app. Authorized, first-party automation only. No fake accounts, no rule-breaking. --- Source: https://mobilerun.ai/apps/x --- title: "Automate YouTube with an AI agent · mobilerun" description: "Automate YouTube with an AI agent on a real phone with real-device identity. Publish and schedule videos, pull analytics and QA playback." url: "https://mobilerun.ai/apps/youtube" category: "Social" --- # Automate YouTube on a real phone. Your agent runs the YouTube app on a real phone with real device and agent identity. It publishes and schedules videos, pulls analytics, and QAs playback on Android and iOS. ## What agents do in YouTube. - **Publish and schedule uploads**: Upload videos to channels you own or manage. The agent sets title, thumbnail, and go-live time, then confirms each post. - **Pull channel analytics**: Read views, watch time, and subscriber changes on channels you manage. The agent captures them and returns structured data. - **QA playback and flows**: Test how a video plays, buffers, and renders on real Android and iOS. Spot a broken embed or stuck player before viewers do. ## Why a real phone. Emulators and headless scripts behave nothing like the real app, so uploads stall and reads fail. mobilerun runs it on real phones on real hardware, with real device and agent identity that passes the checks real apps run, so uploads, reads, and QA stay solid. - Authentic hardware identity. Real phones, not emulators or spoofs, so your agent acts as the account owner. Legitimacy, not evasion. - Any model, your stack. Drive the real phone over API, SDK, or MCP, or hand a task to a chat VA. - Reads the screen, not just pixels. The agent parses the accessibility tree, up to 90% cheaper than vision-only, and runs pay as you go, stateful on request. ## Example tasks - Open YouTube, search my channel, and log each new comment as JSON - Watch the top video for a topic and log each creator's bio - Play a video, enable subtitles, and add it to Watch Later - Open my channel Studio, pull views and likes on recent uploads as JSON ## FAQ **Can I automate YouTube with an AI agent?** Yes. mobilerun gives your agent a real phone running the YouTube app. It can publish, schedule, read analytics, and QA playback on channels you own or are authorized to manage. **Do the real phones read as a real device?** Yes. Every task runs on a real phone that passes the checks real apps run, so your agent is treated as a normal user on genuine hardware. The goal is legitimacy and reliability, not evasion. **Which channels can I automate?** Only your own channels or clients' channels you have permission to manage. mobilerun is built for authorized, first-party automation and QA, never mass account creation. --- Source: https://mobilerun.ai/apps/youtube --- title: "Automate Amazon with an AI agent · mobilerun" description: "Automate Amazon with an AI agent on a real phone with real-device identity. Monitor your own listings, run checkout QA and storefront audits." url: "https://mobilerun.ai/apps/amazon" category: "Commerce" --- # Automate Amazon on a real phone. Your agent opens the real Amazon app on a real phone with real device and agent identity, checks your listings, reads live price and stock, and walks your checkout. ## What agents do in Amazon. - **Monitor your listings**: Check live price and stock on your own or authorized listings. Get a clean feed of what shoppers see, not stale screenshots. - **QA your checkout**: Walk add-to-cart through checkout on a real device. Confirm payment options render, totals add up, and buy flow completes. - **Audit your storefront**: Review your listing and storefront path the way a shopper meets it. See where the mobile experience is confusing or slow. ## Why a real phone. Amazon renders differently on a real mobile device than in a headless browser. Your agent runs on a real phone on real hardware, with real device and agent identity, recognized as genuine, so what it sees is what your shoppers see. - Authentic device identity means the app behaves like it does for a genuine shopper, so your authorized QA and audits reflect the real experience. - Drive it with any model via API, SDK, or MCP, or hand a task to a chat VA. Your stack, your choice of model. - The agent reads the accessibility tree, up to 90% cheaper than vision-only, and runs pay as you go, stateful on request, so you pay only for minutes used. ## Example tasks - open the amazon app, walk the full checkout, and list every payment option - search a product on amazon, screenshot the buy box, and note the price - log into my seller account and cut price 5% on unsold listings - check my amazon orders and export delayed shipments as JSON ## FAQ **Can I automate Amazon with an AI agent?** Yes. It opens the real Amazon app on a real phone and handles search, price and stock reads on your listings, add-to-cart, and checkout QA. Drive it via API, SDK, or MCP, or hand tasks to a chat VA. **Does it read as a normal shopper's phone?** Yes. Each real phone runs genuine Android or iOS and passes the checks real apps run, so the app behaves as it does for a real shopper, keeping your first-party QA and audits accurate. **What Amazon tasks make sense here?** Authorized, first-party work: monitoring price and stock on your own or authorized listings, QA on your checkout and payment options, and auditing your own storefront on real phones. --- Source: https://mobilerun.ai/apps/amazon --- title: "Automate eBay with an AI agent · mobilerun" description: "Run eBay on a real phone. Monitor prices, update your own listings, answer buyers, and QA checkout with an AI agent via API, SDK, or MCP." url: "https://mobilerun.ai/apps/ebay" category: "Commerce" --- # Automate eBay on a real phone. mobilerun gives your AI agent a real phone, Android or iOS, with genuine hardware identity. It tracks price and stock, updates your listings, answers buyers, and QAs checkout. ## What agents do in eBay. - **Monitor price and stock**: Your agent checks prices, stock, and public competing offers on a real device, then flags what changed so you can reprice. - **Manage your own listings**: On its real phone, your agent updates titles, prices, quantities, photos on listings you own, keeping your store current. - **Answer buyers and QA checkout**: Your agent answers buyer messages on your account, walks search, cart, and checkout on a real phone to catch friction early. ## Built on real-device identity. eBay is built for people on phones, so mobilerun runs your agent on a real phone, real Android or iOS, not a spoofed browser. Sessions pass the checks real apps run, so your listings, replies, and test purchases land as legitimate account activity. - Authentic device identity. Your agent works from a real phone, so first-party listings and buyer replies land as legitimate account activity. - Any model, your way. Drive the phone with any model over API, SDK, or MCP, or hand it to a chat VA. - Reads the accessibility tree, up to ~90% cheaper than vision-only. Pay as you go, stateful on request, so you only pay for the minutes you run. ## Example tasks - log into my eBay seller account and cut prices 5% on anything unsold past 7 days - open eBay and pull all buyer messages from the last 24 hours as JSON - check my eBay listings and answer pending buyer questions from saved replies - QA the eBay checkout flow and flag any pre-checked add-ons ## FAQ **Can I automate eBay with an AI agent?** Yes. mobilerun runs the eBay app on a real phone that your agent drives via API, SDK, or MCP. It monitors price and stock, updates your own listings, answers buyers, and QAs checkout. **Do actions come from a real device?** Yes. Every session runs on a real phone, real Android or iOS, on real hardware, with real device and agent identity that passes the checks real apps run. First-party account activity behaves as a normal user's. **What eBay work is this built for?** Your own store and listings, your own buyer messages, price and stock monitoring on public data, and checkout QA. Authorized, first-party automation only. --- Source: https://mobilerun.ai/apps/ebay --- title: "Automate Etsy with an AI agent · mobilerun" description: "Run an AI agent on a real Android or iOS phone to manage your own Etsy shop listings, monitor price and stock, draft buyer replies for approval, and QA checkout." url: "https://mobilerun.ai/apps/etsy" category: "Commerce" --- # Run your Etsy shop on a real phone Point an AI agent at the real Etsy app on a real phone that reads like a normal user's device. It updates listings, tracks price and stock, and drafts replies you approve. ## What the agent does for your shop - **Keep listings current**: The agent opens your shop, updates titles, tags, and photos, and flags listings that drifted from your template. - **Watch price and stock**: The agent checks your prices and inventory on a schedule, catching stockouts and flagging restocks before they cost a sale. - **Reply to buyers with approval**: New buyer messages get read and drafted into a reply you review. Nothing sends until you approve, keeping answers fast. ## Why the real phone reads as real Etsy is mobile-first, and its app behaves like one. mobilerun gives your agent a real phone on real hardware, with real device and agent identity that passes the checks real apps run. Shop management, monitoring, and checkout QA run cleanly on your account. - Genuine hardware identity, first-party access. Your authorized shop runs on a real phone, so listings and buyer messages land reliably. - Any model, your stack. Drive the agent through API, SDK, or MCP, or hand tasks to a chat VA. Bring the model you already use. - Reads the accessibility tree. The agent works from the app's own structure, up to 90% cheaper than vision-only, with pay-as-you-go pricing. ## Example tasks - log into my Etsy shop, open each active listing, and export title, price and stock as JSON - cut the price 5% on any of my listings unsold past 30 days - check my shop inbox and draft replies to open buyer questions - walk the Etsy checkout on my own listing and flag every pre-checked upsell ## FAQ **Can I automate Etsy with an AI agent?** Yes. mobilerun puts the real Etsy app on a real phone with authentic device identity. Your agent drives it via API, SDK, MCP, or chat VA to manage listings, track price and stock, and draft replies you approve. **Does a real phone with real-device identity help my shop?** Yes. Your authorized shop runs on a real phone that passes the checks real apps run. That means clean, reliable first-party access to your own account, not a workaround. **Do I stay in control of what the agent sends?** Always. Buyer replies and listing changes are drafted for you to review, and nothing sends or publishes until you approve it. The agent handles the busywork while you keep the final say. --- Source: https://mobilerun.ai/apps/etsy --- title: "Automate Uber with an AI agent · mobilerun" description: "Automate Uber with an AI agent on a real phone. Book rides and couriers on your own account, confirm fare and ETA, and run navigate-only app QA." url: "https://mobilerun.ai/apps/uber" category: "Commerce" --- # Automate Uber on a real phone. Your agent books rides and couriers in Uber on a real phone, signed in to your own account. It passes the checks real apps run, then confirms fare, driver and ETA. ## What agents do in Uber. - **Book rides on your own account**: Dispatch a ride from your own account, set pickup and drop-off, and confirm the fare, driver and ETA before the trip starts. - **Order couriers programmatically**: Send a courier request over the API from your own account, pass the addresses, and read back the quote and confirmation. - **Navigate-only app QA**: Open the Uber app on real Android and iOS builds, walk the core screens, and confirm each loads without a paid action. ## Why a real phone. Uber runs on a phone. Your agent drives a real phone with a genuine hardware fingerprint, signed in to your own account, so It is real hardware end to end. It passes the checks real apps run, keeping first-party runs reliable and deliverable. - A real phone with real device and agent identity, signed in to your own account, keeps every run first-party so bookings land cleanly. - Drive it from any model over API, SDK or MCP, or hand a task to the chat VA. - The agent reads the accessibility tree, up to 90% cheaper than vision-only, and you pay only for what runs. ## Example tasks - fresh install Uber, sign up, verify by SMS, assert the home screen loads - open Uber, enter pickup and destination, list every ride tier and fare, don't book - walk the Uber payment screen, list all payment methods, flag any pre-checked upsell - open Uber trip history, list past rides with dates and totals, don't rebook ## FAQ **Can I automate Uber with an AI agent?** Yes. mobilerun gives your agent a real phone running the Uber app, driven over API, SDK or MCP. It books rides and couriers on your own account, confirms the fare and ETA, and runs navigate-only app QA. **Does it work as a normal user?** Yes. The real phone carries real hardware, real device and agent identity and passes the checks real apps run, so It is real hardware end to end. Signed in to your own account, it books rides just as you would by hand. **Can I test the Uber app on real devices?** Yes. Run navigate-only checks that open the app on real Android and iOS builds and confirm the core screens load, with screenshots and steps you can post to CI. --- Source: https://mobilerun.ai/apps/uber --- title: "Automate Vinted with an AI agent · mobilerun" description: "Run an AI agent on a real phone to manage your own Vinted listings, monitor prices, and draft buyer replies for your approval. Pay as you go." url: "https://mobilerun.ai/apps/vinted" category: "Commerce" --- # Automate Vinted on a real phone. Give an AI agent a real phone that runs Vinted like you do. It is compatible with the checks real apps run. Manage listings, watch prices, answer buyers. ## What agents do in Vinted. - **Manage your own listings**: Draft, update, and refresh listings on your own account. The agent edits titles, prices, and photos in the real app. - **Monitor prices on what you sell**: Point the agent at what you sell and let it check comparable prices on a schedule. It flags when it's time to reprice. - **Answer buyers, with your approval**: The agent drafts replies to questions on your listings and waits for your sign-off before anything sends. ## Why a real phone matters. Vinted is mobile-first and treats accounts as real people on real devices. mobilerun gives the agent a phone on real Android or iOS, not a spoofed emulator, so it passes the checks real apps run. State persists; pay only for minutes used. - Real hardware, real device and agent identity. Your account runs on a real phone that passes the checks real apps run. - Any model, your way. Drive the phone from any LLM over our API, SDK, or MCP, or hand tasks to a chat assistant. - Cheaper by default. The agent reads the accessibility tree instead of screenshots, up to 90% cheaper than vision-only, on pay as you go, stateful on request. ## Example tasks - Open Vinted, capture my store's active listings, and export them as JSON - Cut the price 5% on anything unsold past 7 days in my Vinted store - Log in to Vinted, answer pending buyer messages on my listings, and summarize each - QA the Vinted checkout: list every payment option and flag pre-checked upsells ## FAQ **Can I automate Vinted with an AI agent?** Yes. mobilerun runs Vinted on a real phone and lets an AI agent drive it via API, SDK, MCP, or a chat assistant. Point it at your own account to manage listings, monitor prices, and draft replies for approval. **Does this use a real device or an emulator?** A real one. Your account runs on a real phone, Android or iOS, with real device and agent identity, recognized as genuine. We automate only your own account, for legitimacy, not disguise. **Will the agent message buyers without me?** Only if you let it. By default the agent drafts replies and waits for your approval before anything sends, so you stay in control of every message on your listings. --- Source: https://mobilerun.ai/apps/vinted --- title: "Automate Walmart with an AI agent · mobilerun" description: "Drive the Walmart app on real phones with an AI agent. Monitor your own catalog, manage your Marketplace listings, and QA checkout in every market you sell in." url: "https://mobilerun.ai/apps/walmart" category: "Commerce" --- # Automate Walmart on a real phone Point an AI agent at Walmart on your own real phone. Genuine hardware identity keeps catalog monitoring, listing work, and buyer-flow QA solid in every market you sell in. ## What teams automate on Walmart - **Monitor your own catalog and pricing**: An agent opens the Walmart app, reads your own listing pages, and logs price, availability, and buy-box state on a schedule. - **Manage your Marketplace listings**: On the seller accounts you own, check titles, images, and stock, flag pages out of policy, and confirm updates landed. - **QA the shopping and checkout flow per market**: Walk the buyer path on real Android and iOS phones: search, add to cart, apply an offer, and check out across your markets. ## Why it works on mobilerun Walmart is built for real shoppers on real phones. mobilerun gives your agent one that passes the checks real apps run. The agent sees what a customer sees, and your first-party work on accounts and catalog you own stays reliable. - Real hardware, real device and agent identity. Every session runs on a real phone recognized as genuine, so your results stay reliable. - Any model, your stack. Drive the app from any model over API, SDK, or MCP, or hand a task to the chat VA. No rewrite when you switch models. - Reads the accessibility tree. The agent works from the app's structure, ~90% cheaper than vision-only, and pays as you go, stateful on request. ## Example tasks - Open Walmart, add a listed item to cart, and reach the checkout screen. - Fresh install Walmart, sign in to my account, and confirm the home screen loads. - Search Walmart for a product and capture its price and availability as JSON. - Browse Walmart weekly deals and list the top five discounts you find. ## FAQ **Can I automate Walmart with an AI agent?** Yes. mobilerun runs the Walmart app on a real phone and lets your agent drive it over API, SDK, MCP, or the chat VA. Use it for authorized work: catalog monitoring, listing management, and buyer-flow QA. **Does it run on a real device?** Yes. Every session runs on a real phone, not an emulator. It passes the checks real apps run, so your QA results stay true to production. **How does mobilerun keep automation costs down?** The agent reads the app's accessibility tree instead of vision alone, ~90% cheaper per step. Sessions are pay as you go, stateful on request, so you only pay for the phone time you use and pick up where you left off. --- Source: https://mobilerun.ai/apps/walmart --- title: "Automate Chrome with an AI agent · mobilerun" description: "Automate Chrome on a real phone. An AI agent opens URLs, signs into your web apps, and runs web plus app flows end to end on a real Android or iOS device." url: "https://mobilerun.ai/apps/chrome" category: "Work" --- # Automate Chrome, in the cloud. Your agent drives Chrome on a real phone with genuine hardware identity. It opens URLs, searches, signs into your web apps, and loads the desktop site a normal user sees. ## What agents do in Chrome. - **Open URLs and search**: The universal glue step. Point the agent at any link or query and it navigates, reads the page, and pulls the data you need. - **Sign into your web apps**: Log into your own or a client's authorized accounts, land on the dashboard, and pull the numbers or trigger the task. - **Run web and app flows end to end**: When a task starts in the browser and ends in a native app, one agent handles both on the same phone. No broken chain. ## Why a real phone is the fix. Headless browsers get blocked when a page must trust the visitor. Chrome on a mobilerun real phone loads as a normal user on real Android or iOS hardware that passes the checks real apps run, so the reliable path is the default for authorized flows. - Real hardware, real device and agent identity means pages, logins, and sessions treat the visit as a real user on a real Android or iOS device. - Drive it with any model via API, SDK, or MCP, or hand a task to the chat VA. - Reads the accessibility tree, up to ~90% cheaper than vision-only, on pay as you go, stateful on request phones. ## Example tasks - open Chrome, load our staging site, log in, and confirm the dashboard renders - open Chrome, visit our storefront, capture the checkout page, and diff vs yesterday - open Chrome, walk our pricing page, list every plan and pre-checked upsell - open Chrome, open our signup flow, fill test data, and verify the SMS step ## FAQ **Can I automate Chrome with an AI agent?** Yes. Your agent drives Chrome on a real phone via API, SDK, or MCP. It opens URLs, searches, signs into your web apps, and runs the flow end to end. **Does the browser read as a normal user?** Yes. Chrome runs on a real phone with an authentic device identity, so pages and logins see a genuine visitor on real hardware. That legitimacy makes authorized, first-party automation land reliably. **Can it handle a task that spans web and a native app?** Yes. The same phone runs Chrome and your native apps, so one agent carries a task from the browser into the app without a handoff. --- Source: https://mobilerun.ai/apps/chrome --- title: "Automate Google Maps with an AI agent · mobilerun" description: "Google Maps automation on a real phone. Let an AI agent check your local rank from real locations and QA navigation, in any market you sell in." url: "https://mobilerun.ai/apps/google-maps" category: "Work" --- # Automate Google Maps on a real phone. Your agent opens Google Maps on its own real phone, an Android or iOS device with a genuine hardware fingerprint. Real location, real network, so it sees what customers see. ## What agents do in Google Maps. - **Check your local rank from real locations**: See where your business ranks from a real phone on a real IP, not a datacenter. Your agent runs the search a customer runs. - **Track your visibility per market**: Run the same query across every market you care about, on devices located there, and compare how your listing surfaces. - **QA navigation and head-unit flows**: Drive turn-by-turn, route, and hand-off flows. Your agent checks navigation and head-unit behavior before users do. ## Why a real phone. Local Maps results depend on where requests come from; a datacenter IP or emulator distorts them. mobilerun runs your agent on a real Android or iOS phone with a real location and network, so results match reality. Drive it via API, SDK, MCP, or chat VA. - Real hardware, real device and agent identity. Real phones that pass the checks real apps run, so what you measure matches what a real local user sees. - Any model, any framework. Drive the phone via API, SDK, or MCP, or just describe the task to the chat VA. - Reads the accessibility tree, up to about 90% cheaper than vision-only, so multi-market rank sweeps stay affordable. Pay as you go, stateful on request. ## Example tasks - open my business profile in google maps, review new customer reviews, and reply to each - search my store category nearby, capture the top listings and ratings as JSON - check my business hours and address on google maps, flag anything outdated - open google maps, walk the search-to-directions flow, and confirm each step loads ## FAQ **Can I automate Google Maps with an AI agent?** Yes. mobilerun gives your AI agent a real Android or iOS phone, and it drives Maps like a person, searching, checking rank, and running navigation. Connect any model via API, SDK, or MCP, or use the chat VA. **Does it look like a normal user?** It is a normal user. Your agent runs on a real phone that passes the checks real apps run and reads as an ordinary device in an ordinary place. That legitimacy makes your rank checks and QA trustworthy. **Can I check how my business ranks in different cities?** Yes. Run the same search on real phones in each market you care about and compare the local results side by side. Because each check runs on a real device in that region, the ranking matches what locals see. --- Source: https://mobilerun.ai/apps/google-maps --- title: "Automate LinkedIn with an AI agent · mobilerun" description: "Automate LinkedIn on a real phone with real-device identity. First-party outreach, monitoring and research on your authorized accounts, via API or MCP." url: "https://mobilerun.ai/apps/linkedin" category: "Work" --- # Automate LinkedIn on a real phone. Your agent runs the LinkedIn app on a real phone, one clean identity per rep. It sends authorized outreach at a human pace and files rep-ready notes into your CRM. ## What agents do in LinkedIn. - **Authorized outreach, one rep per phone**: Your agent drafts, personalizes, and sends first-party outreach at a human pace on your own accounts, one identity per rep. - **Keep your CRM in sync**: Read the profile and company details a rep already sees, and hand your CRM clean, current notes. First-party, not harvesting. - **Monitor your feed and presence**: Track posts, mentions, and engagement across accounts you own. Your agent watches the feed and reports what matters. ## Why a real phone. LinkedIn is a mobile app built for a real device. mobilerun runs it on a real phone, Android or iOS, that passes the checks real apps run. That genuine hardware identity is what authorized outreach needs. Any model drives it over API, SDK, or MCP. - Real hardware, real device and agent identity. One clean real phone per rep means legitimate accounts and outreach that lands, not a browser faking a person. - Any model, your stack. Drive the real phone over API, SDK, or MCP, or hand a task to a chat VA. - Reads the accessibility tree. Your agent uses the screen's structure, up to 90% cheaper than vision-only, on pay as you go, stateful on request real phones. ## Example tasks - Log into our authorized LinkedIn account, publish the draft post, confirm it appears in the feed - QA the LinkedIn login flow, verify the code, assert the home feed loads - Open our company page notifications, reply to new comments, log each thread as JSON - Track our latest LinkedIn post reach, capture the analytics screen, save the numbers ## FAQ **Can I automate LinkedIn with an AI agent?** Yes. mobilerun runs the LinkedIn app on a real phone that your AI agent drives via API, SDK, or MCP. Point it at your own or your clients' authorized accounts for outreach, CRM sync, and monitoring. **Does it read as a normal user's phone?** Yes. Each rep gets one real phone, Android or iOS, that passes the checks real apps run. LinkedIn sees the human-like signals of any person on their own phone, keeping outreach legitimate. **How is this different from ban-evasion tools?** It is the opposite. mobilerun is for first-party, authorized automation on accounts you own or are permitted to run, always at a human pace. No spoofing, just genuine accounts run by your own reps. --- Source: https://mobilerun.ai/apps/linkedin --- title: "Automate Alibaba with an AI agent · mobilerun" description: "Automate Alibaba sourcing with an AI agent on a real phone. Read your supplier inbox and messenger, extract quotes, MOQ and terms as JSON. Pay as you go." url: "https://mobilerun.ai/apps/alibaba" category: "Commerce" --- # Automate Alibaba sourcing on a real phone. Your agent signs in to your own Alibaba and 1688 account on a real Android or iOS phone, reads your supplier inbox and messenger, and returns quotes, MOQ, and terms as JSON. ## What agents do in Alibaba. - **Read your supplier inbox and messenger**: Point your agent at your Alibaba and 1688 inbox. It reads supplier replies and messenger threads and returns who quoted what. - **Extract quotes, MOQ, and terms as JSON**: Your agent pulls unit price, MOQ, lead time, and payment terms from each thread and returns clean JSON you can compare. - **Search suppliers and negotiate**: Search suppliers, shortlist the best fits, and draft outreach and counter-offers. It waits for your yes before sending. ## Why a real phone. Alibaba and 1688 are built for phone buyers, and the app carries messenger threads a headless scraper never sees. Your agent runs on real Android or iOS hardware that passes the checks real apps run, so your inbox loads and sessions hold across runs. - Genuine hardware identity. A real Android or iOS phone keeps your session trusted, so messages, quotes, and search load like any buyer's phone. - Any model, any stack. Drive the phone with any model over API, SDK, or MCP, or hand a sourcing task to a chat VA. - Reads the accessibility tree, up to about 90% cheaper than vision-only. Pay as you go, stateful on request, so you pay only for the minutes you run. ## Example tasks - open my alibaba supplier inbox, summarize new replies, and return each quote as JSON - search 1688 for a 40mm speaker driver and shortlist 5 suppliers with price and MOQ - read my 1688 messenger threads and extract lead time and payment terms per supplier - draft counter-offers for 3 suppliers on my account and queue them for my approval ## FAQ **Can I automate Alibaba with an AI agent?** Yes. mobilerun runs the Alibaba app on a real phone, and your agent drives it over API, SDK, or MCP. It reads your inbox and messenger, extracts quotes, MOQ, and terms as JSON, and drafts messages you approve. **Is this a real device or an emulator?** Each real phone is real Android or iOS hardware on real hardware, with real device and agent identity, and passes the checks real apps run. As a genuine device, the Alibaba app behaves normally and your inbox holds across runs. **Does the agent message suppliers on its own?** Only with your approval. It reads and extracts freely, but every supplier message and counter-offer is drafted and queued for your yes before anything sends. You stay in the negotiation, on your own account. --- Source: https://mobilerun.ai/apps/alibaba --- title: "Automate AliExpress with an AI agent · mobilerun" description: "Automate AliExpress on a real phone on real hardware, with real device and agent identity. Point an AI agent at price and stock monitoring, order tracking, and market research." url: "https://mobilerun.ai/apps/aliexpress" category: "Commerce" --- # Automate AliExpress on a real phone. Your agent opens AliExpress on a real phone that reads as a shopper's device. It monitors price and stock by region, tracks orders, and runs per-market sourcing research. ## What agents do in AliExpress. - **Monitor price and stock across regions**: Read live prices and stock on products and stores you follow, per ship-to country. See what shoppers see, not a stale export. - **Track your own orders**: Watch your orders end to end: confirmation, shipping, delivery. The agent reports where each parcel stands on your account. - **Run sourcing research per market**: Compare products, prices, and stores across regions you sell into. Same search per market, one clean, comparable feed. ## Why a real phone. AliExpress renders differently on a real mobile device, and prices, shipping, and stock shift by region. Your agent runs on real hardware that passes the checks real apps run, so what it sees is what your shoppers see in that market. - Authentic device identity makes the app behave as it does for a genuine shopper, so your monitoring and research reflect the real market. - Drive it with any model via API, SDK, or MCP, or hand a task to a chat VA. Your stack, your choice of model. - The agent reads the accessibility tree, up to 90% cheaper than vision-only, and runs pay-as-you-go so you only pay for the minutes you use. ## Example tasks - open aliexpress shipping to Germany and check price and stock on my saved product - track my open aliexpress orders and report shipping status for each - run the same product search across US, DE, and UK and return prices as JSON - monitor 5 stores I follow and flag any price or stock change ## FAQ **Can I automate AliExpress with an AI agent?** Yes. Your agent opens the real AliExpress app on a real phone for search, price and stock reads by region, order tracking, and per-market sourcing research. Drive it via API, SDK, or MCP, or hand to a chat VA. **Does it read as a normal shopper's phone?** Yes. Each real phone runs real Android or iOS and passes the checks real apps run, so AliExpress behaves as it does for a genuine shopper. That legitimacy keeps your monitoring and research accurate. **Is AliExpress the same as Alibaba?** No. AliExpress is the consumer marketplace; Alibaba is B2B wholesale. This page covers AliExpress: monitoring your products, tracking your orders, and per-market price and sourcing research on real phones. --- Source: https://mobilerun.ai/apps/aliexpress --- title: "Automate Shein with an AI agent · mobilerun" description: "Automate Shein on a real phone with an AI agent. Monitor prices, stock and trends, track your own orders, and QA checkout per market. Pay as you go." url: "https://mobilerun.ai/apps/shein" category: "Commerce" --- # Automate Shein on a real phone. Your agent runs the real Shein app on a real phone with real device and agent identity. It watches prices, stock, and trends, tracks your orders, and QAs checkout per market. ## What agents do in Shein. - **Monitor prices, stock, and trends**: The agent opens Shein on a real device and reads live prices, stock, and trends in the categories you follow, on a schedule. - **Track your own orders**: Point the agent at your own account to check order status, shipping, and delivery. It flags delays before buyers ask. - **QA the shopping and checkout flow per market**: Walk search, cart, and checkout on real Android and iOS phones per market. Confirm prices, currencies, and totals add up. ## Why a real phone. Shein is built for phones and renders differently on a real device than in a headless browser. mobilerun runs your agent on a real phone that passes the checks real apps run, so it sees what shoppers see and your monitoring and QA stay true. - Real hardware, real device and agent identity. Sessions run on a real phone recognized as genuine, so monitoring and QA read like a real shopper. - Any model, your stack. Drive the Shein app from any model over API, SDK, or MCP, or hand a task to the chat VA. Switch models, no rewrite. - Reads the accessibility tree, up to ~90% cheaper than vision-only. Sessions are pay as you go, stateful on request: keep state, pay for minutes used. ## Example tasks - open shein shipping to the US and check price and stock on my tracked items - track my shein orders end to end and report delivery status - QA the shein search-to-checkout flow and confirm each step loads - monitor prices on my saved shein products across 3 markets and return JSON ## FAQ **Can I automate Shein with an AI agent?** Yes. mobilerun runs the real Shein app on a real phone. Your agent drives it via API, SDK, MCP, or chat VA: monitor prices, stock, and trends, track orders, and QA checkout, all first-party and authorized. **Does it run on a real device?** Yes. Every session runs on a real phone, not an emulator, with a genuine hardware fingerprint. It passes the checks real apps run, so the app behaves as it does for a real shopper and your QA stays true. **What Shein tasks make sense here?** Authorized, first-party work: watching prices, stock, and trends on public catalog data, tracking orders on your account, and QA on your shopping and checkout flow, all on real phones. --- Source: https://mobilerun.ai/apps/shein