Early access · The first phone for your agent

Virtual phone infrastructure for AI agents.

ERIUS PHONE gives AI agents real Android phones in the cloud — devices, not phone numbers — driven over one HTTP API and MCP. Every phone is isolated, keeps its apps and sign-ins, and runs in parallel with the rest.

Call Use apps Test Audit Automate

Agents work in browsers. People live in apps.

Erius Phone is a real Android phone in the cloud that your AI agent controls over an API. It can try your app the way a user would, or use mobile apps on a phone of its own.

What it is

Not a simulator. A phone.

Two gaps, one device. If you ship an Android app, there's no easy way to see how a real user — or a real AI agent acting as one — gets through it on a real phone. And if you build agents, they're stuck in browsers and APIs, outside the apps people actually use. Erius Phone is an Android device for AI agents — a full virtual Android phone with the real operating system, real apps, real Google Play Store, real browser — that your agent uses through the same surface a person does: the touchscreen, driven by our AI agent phone API.

Search results and on-screen keyboard on the agent's Android phone
agent viewui tree + vision
// accessibility tree, trimmed
EditText   "Signal"       focused
TextView   "Apps"
Item       "MeshCore Signal Tester"
           bounds [32,272][688,400]  clickable
Item       "Signal Generator"
           bounds [32,452][688,540]  clickable
Keyboard   visible  ime="latin"

// next action
tap("MeshCore Signal Tester")

Real Android

The full OS boots and runs. Apps behave the way they do on a handset — permissions, notifications, keyboards, back stack and all.

Every phone also carries a Samsung S25-class device profile (model, brand and manufacturer) instead of a generic emulator default. The system underneath is Android 13.

Screenshot captured on an Erius Phone device; tree simplified for illustration.

Real apps, real store

Install from Google Play, from an alternative store, or straight from your APK. The agent's apps stay installed on its phone between sessions.

Looks before it taps

No brittle selectors written in advance. The agent reads the accessibility tree and a screenshot each step, and decides what to do from what's on screen.

One API, every gesture

Tap, type, swipe, launch, install, read, screenshot — plain HTTP calls any agent framework can make.

Real microphone input, too: the agent can play audio into any app that uses the mic — voice assistants, recording apps, voice verification flows.

Video into the camera is in opt-in beta on new devices.

Any app

Any app on Google Play. No API required.

Most apps don't publish an API your agent could call. Erius Phone doesn't need one — the agent uses the touchscreen, exactly like you do: it taps, reads, and scrolls through whatever is on screen. If you built the app yourself, it can also audit it the way a real user experiences it, not just by reading your source code.

Install it, then use it

If it's on Google Play, the agent can install it and use it — no integration, no partnership, no SDK. Some apps refuse to run on virtual devices; we'll tell you plainly when one does.

The same touchscreen you use

No hooks into the app's internals. The agent sees the screen and acts on it, the way a person would.

Audit your own app honestly

Reading your source code tells you what the app should do. The agent tells you what actually happens when someone uses it.

How it works

From APK to report in four steps.

Flow shown is illustrative; the packaged report in step 4 is coming soon. Read the real API reference →

  1. dev_7f3aready
    provisioned for youisolated container
    01

    Get your agent's phone

    During early access we provision your dedicated Android device by hand and hand you its API key — running in its own isolated environment.

  2. Your agent 
    tap     "Sign up"
type    "hello"
    Its phone 
    screen  → tree + png
    02

    Your agent gets an API

    Touch-level control over HTTP, plus a structured read of whatever is on screen.

  3. dev_7f3a / install
    >_ install app-release.apk
   goal "sign up, add an item, check out"
    03

    Upload your APK

    Your agent installs it, opens it, and works through the flows you give it in plain language — like a new user would.

  4. checkout  PASS  12 steps
signup    FAIL  step 6
→ report.html
    04

    Get results

    Today your agent pulls a screenshot, the screen's UI tree and the crash log at any step through the API. A packaged report with pass/fail per flow is coming soon.

Try it live

Poke a real Android phone right now.

This is the same kind of device your agent gets, live, not a video. Tap to press, drag to scroll, and use Back and Home to get around. You get the touchscreen your agent uses.

checking device…

This is a real shared Android device — one demo session at a time, 90 seconds, resets after each turn.

Use cases

Two problems it solves.

Primary

App QA, done by something that actually uses the app

2/3flows passed · example

Clicking through every flow by hand on every release is slow, and scripted UI tests break the moment a screen changes — so the bugs that slip through are the ones real users find first. Instead, give your agent an APK and a list of things a user should be able to do. It installs the build on a real Android device, works through each flow by reading the screen, and tells you where it got stuck — with the screenshot to prove it.

  • Install straight from your APK, every build
  • Flows written as goals, not selector scripts
  • Screenshot and crash log at every step, through the API
  • Coming soon: goal-based QA runs with pass/fail reports
run #42 · example · coming soon
onboarding  PASS  7 steps   7 shots
search      PASS  5 steps   5 shots
checkout    FAIL  crash at step 6
            stack trace attached

The report shown previews the packaged format we're building. Today your own agent runs the test through the device API and collects the screenshots and crash log itself.

Also

Agent automation on real Android

A lot of what people do on a phone happens inside apps that have no website and no public API — and an agent working through a browser can't reach them. On its own phone, it can: anything a person can do on Android, your agent can now do too.

  • Real apps from Google Play
  • A browser that's a real mobile browser
  • State that persists between sessions

Sign-ins stay human. Account sign-ins and other sensitive steps are done once by a person, by design. The agent works inside the session you've set up — it doesn't handle your credentials. Some apps also restrict virtualized devices; we'll tell you plainly when one does.

A phone showing an incoming Telegram video call from the agent, a stylized AI avatar waving on screen
Product render commissioned for ERIUS PHONE — the agent's Telegram and WhatsApp video-call screens.

Now with video

Your agent has a face
and a voice now.

Call it, or have it call you — a real one-to-one video or voice call, not just text and voice notes. Conference calls with several people are coming next.

  • Call it, or it calls you

    Real one-to-one video or voice over WhatsApp or Telegram.

  • A face, not just a voice

    On a video call your agent appears as an avatar and talks with you live.

  • Coming: conference calls

    Adding it to a call with partners or clients is next on the roadmap.

Give your agent a voice

One-to-one calls over WhatsApp and Telegram.

For your own agent

Give your agent a phone of its own.

You have a phone. Your AI assistant has been living in a chat window. Give it a real Android phone — its own home screen, its own apps, its own browser — and stop lending it yours.

  • Somewhere to put its apps

    It installs apps from Google Play, and they're still there tomorrow.

  • It scrolls. It types. It taps.

    Real apps and a real mobile browser, driven by your agent over a simple API.

  • You do the sign-ins, once

    Like setting up a phone for someone new: you log in to the accounts it needs, then it takes it from there. It never handles your passwords.

Give your agent a phone
An agent's own Android phone home screen, with a live James AI-agent widget
Product renders commissioned for ERIUS PHONE.

Compare

ERIUS PHONE next to the alternatives.

Pick one. You get what ERIUS PHONE has that it doesn't, and what it has that ERIUS PHONE doesn't yet.

ERIUS PHONE vs.

ERIUS PHONE vs. Mobilerun

ERIUS PHONE has · Mobilerun doesn't

  • One-to-one voice and video calls with your agent over WhatsApp or TelegramMobilerun's home, pricing and docs pages don't mention voice or video calling
  • A flat monthly preview price per phone: its running time is not meteredMobilerun plans meter powered-on time: 600 minutes on the roughly €18 plan, then about €0.027 a minute
  • One persistent Android 13 phone for €39 a month (preview)Mobilerun's dedicated always-on Android is about €45/mo

Mobilerun has · ERIUS PHONE doesn't yet

  • Self-serve signup with a free plan (60 device minutes)ERIUS PHONE: no self-serve signup yet, no free plan
  • Real physical iPhones (about €179/mo)ERIUS PHONE is Android only
  • Residential IPs and receive-only SMS numbersWe have no residential IP, SIM or SMS number
  • A WebRTC live stream and a hosted MCP serverNo live stream for customers yet; our MCP is a package you run locally
  • A built-in agent billed in creditsYou bring your own model

Mobilerun details checked on its pricing and docs pages, 10 October 2026. Their prices are in US dollars; the euro amounts here are approximate, converted at the ECB reference rate of 13 October 2026 (1 EUR = 1.1188 USD). Full Mobilerun comparison →

ERIUS PHONE vs. mobile-mcp

ERIUS PHONE has · mobile-mcp doesn't

  • Hosted: nothing to install on your machine but an HTTP clientmobile-mcp runs locally and needs Node.js 20+, Xcode or Android tools, and your own device or emulator switched on
  • One persistent phone: installed apps and sign-ins are still there tomorrowMobile Next Cloud describes isolated on-demand sessions
  • A flat preview price of €39 a month, no device minutes to countMobile Next Cloud: about €26 buys 200 minutes a month, then about €0.13 a minute
  • Voice and video calls with your agent over WhatsApp or TelegramNeither the mobile-mcp README nor the Mobile Next Cloud page mentions calling

mobile-mcp has · ERIUS PHONE doesn't yet

  • Free and open source (Apache-2.0)ERIUS PHONE is neither
  • iOS: simulators and real iPhonesERIUS PHONE is Android only
  • Real devices in Mobile Next CloudOurs are virtualized, so some banking, DRM and game apps refuse to run
  • Self-serve signup, free 10 minutes a day, no cardERIUS PHONE: no self-serve signup yet, no free tier
  • Session traces and replayWe have no session replay

mobile-mcp and Mobile Next Cloud details checked on the repository and cloud page, 10 October 2026. Their prices are in US dollars; the euro amounts here are approximate, converted at the ECB reference rate of 13 October 2026 (1 EUR = 1.1188 USD). Full mobile-mcp comparison →

ERIUS PHONE vs. Hardline

ERIUS PHONE has · Hardline doesn't

  • The screen as an accessibility tree with element refs, plus tap-by-text and wait-for-textHardline's published MCP tools work from screenshots and x/y taps; typing is ASCII-only
  • Preview price €39 a month for one phone, €129 a month for threeHardline is about €72/mo, or about €107/mo with a camera on the screen
  • APK install and crash logs through the APINot in Hardline's published tool list
  • Voice and video calls over WhatsApp or Telegram, and audio into the phone's microphoneHardline's published tool list has no audio tools

Hardline has · ERIUS PHONE doesn't yet

  • A real physical Android handset in the USOurs are virtual and not Play Protect certified, so some banking, DRM and game apps won't run
  • A real SIM, a real US number and a mobile-data IPWe have no SIM, no number, no carrier IP
  • Sign up and buy on your own today, even by an agent over MCP (crypto only)ERIUS PHONE: no self-serve signup yet, and no payment is taken at all
  • A hosted MCP endpointOur MCP is a package you run locally

Hardline details checked on hardlinephone.com, 10 October 2026. Their prices are in US dollars; the euro amounts here are approximate, converted at the ECB reference rate of 13 October 2026 (1 EUR = 1.1188 USD). Neither offers an iPhone today. Full Hardline comparison →

ERIUS PHONE vs. Phonebox

ERIUS PHONE has · Phonebox doesn't

  • One-to-one voice and video calls with your agent over WhatsApp or TelegramPhonebox states that it “doesn't make or receive calls”
  • A flat preview price of €39 a month per phone, its running time not meteredPhonebox is about €0.054 a minute, which is cheaper below about twelve hours a month (ECB rate of 13 October 2026)
  • A phone that isn't parked between tasks, so there is no session clock to managePhonebox phones park when idle; a session runs three hours at most

Phonebox has · ERIUS PHONE doesn't yet

  • Self-serve in minutes: about €1.79 free credit, no cardERIUS PHONE: no self-serve signup yet, no free credit
  • Per-second billing, and parked phones are freeThe better buy for short, bursty test runs
  • A hosted MCP endpoint, one command to connectOur MCP is a package you run locally
  • A live view link for handing the phone to a humanNo live view for customers yet
  • Settable location, locale and timezone

Phonebox details checked on phonebox.dev and its docs, 10 October 2026. Their prices are in US dollars; the euro amounts here are approximate, converted at the ECB reference rate of 13 October 2026 (1 EUR = 1.1188 USD). Full Phonebox comparison →

ERIUS PHONE vs. Opposable

ERIUS PHONE offers

  • Cloud Android 13 phones, each in its own isolated containerOpposable's cloud phones run Android 15 (Starter about €17/mo, sleeps when idle; Always-on about €44/mo)
  • Three phones on the Team preview plan for €129 a monthOpposable Cloud Team: three always-on phones for about €133/mo
  • An HTTP device API and an installable MCP serverOpposable also connects agents over MCP, and its app has a REST API

Opposable offers · ERIUS PHONE doesn't yet

  • A free app that lets an agent drive the phone you already ownERIUS PHONE phones are cloud only, with no SIM or number
  • iPhone control through a paired Mac (beta)ERIUS PHONE is Android only
  • An agent model that runs on the phone itselfERIUS PHONE is driven by your own agent over the API or MCP

Opposable details as published on its own website, getopposable.com, checked on 14 October 2026. Their prices are in US dollars; the euro amounts here are approximate, converted at the ECB reference rate of 13 October 2026 (1 EUR = 1.1188 USD). Full Opposable comparison →

ERIUS PHONE is in early access: we onboard each team personally and issue devices and API keys directly, with self-serve signup and online payment to follow. €39 and €129 a month are preview prices. Competitor prices and features change, so check the vendor's own site before you decide. Product names belong to their owners, and ERIUS PHONE is not affiliated with them.

Built for isolation

Every phone is its own phone.

Your agent's device isn't shared, pooled, or reset into someone else's hands.

Container per device
Each customer's phone runs in its own isolated container. No shared filesystem, no shared app data.
Network isolation
Every device sits on its own isolated network. Phones can't see each other.
Full control via API
Everything the agent does goes through the API — every call is explicit and scoped to your device.
Real Android
A full virtualized Android system — not an emulator skin and not a screenshot simulator.

Pricing

Simple plans, priced per phone.

These are our early-access preview prices. Final launch pricing will be published before general availability and may still change.

Starter
€39/mo
For solo developers trying their agent on a real phone.
Team
€129/mo
For teams running app QA on every build.
Enterprise
Contact us
For organizations with volume or compliance needs.

Preview pricing for early-access teams, in euros. Call minutes are priced separately. Subject to change before general availability. Compare plans →

See plans & pricing FAQ

Give your agent a phone.

Then let it try your app the way your users will.

Request a device

Already listed and discoverable on

GitHub PyPI MCP Repository SaaSHub Agent Locker AgentsIndex 独立开发变现周刊 HelloGitHub 阮一峰的网络日志 Awesome MCP Servers

Live demo · shared device

A real Android phone

Live screen of the shared demo Android phone

Connecting to the device…

1:30 left in this session
  • Tap the screen to touch it
  • Drag to swipe or scroll lists
  • ◁ ○ ▢ are Back, Home and Recents

    This is a real shared Android device — one demo session at a time, 90 seconds, resets after each turn. The screen refreshes about once a second, so give it a moment after each tap. Closing this panel ends your turn straight away for the next person.