---
title: "Real phone for AI agents"
url: "https://mobilerun.ai/real-phone-for-ai-agents"
---

# Real phone for AI agents

A real phone for an AI agent is a device in a data centre that an agent drives over an API, with genuine device identity, its own SIM, its own network route, and state that survives between sessions.

Four layers, and a gap in any one of them shows:

1. **The device.** Cloud-hosted Android and iOS with persistent app state and device location configurable for any country or region.
2. **The identity.** One phone, one consistent identity, rather than a fingerprint regenerated per run.
3. **The network.** A route out whose country matches the device. See https://mobilerun.ai/connect
4. **The number.** A real eSIM, so verification codes are readable in-session. See https://mobilerun.ai/esim

**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.

---

Source: https://mobilerun.ai/real-phone-for-ai-agents
Full site as markdown: https://mobilerun.ai/llms-full.txt