Early access · Real Android for AI agents

The first phone for your agent.

Agents work in browsers. People live in apps.

Erius Phone gives your AI agent a real Android device it controls over an API — so it can try your app the way a user would, or use mobile apps on a phone of its own.

agent session · live demo

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 a full virtual Android device — 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.

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.

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.

How it works

From APK to report in four steps.

Flow shown is illustrative. 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

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

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

    Get results

    A step-by-step record of what happened: screenshots at every step, crash reports, and pass/fail per flow.

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, hand over an APK and a list of things a user should be able to do. The agent 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 at every step
  • Crash reports and pass/fail per flow
run #42 · app-release.apk · example
onboarding  PASS  7 steps   7 shots
search      PASS  5 steps   5 shots
checkout    FAIL  crash at step 6
            stack trace attached

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.

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

A gift idea for the holidays — or any Tuesday.

An app store open on an agent's own Android phone
Real screenshot from an Erius Phone device.

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, announced at launch.

Early-access teams get preview pricing. Final plans will be published before general availability.

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

No plan prices have been set yet.

See plans & pricing FAQ

Give your agent a phone.

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

Request a device

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.