# ERIUS PHONE — Cloud Android phone and tablet an AI agent controls over a plain HTTP API.

> Source: The Agents Index — https://theagentsindex.com/erius-phone (structured, researched, re-verified)
> Facts last verified: 2026-10-09

ERIUS PHONE is a cloud Android device for AI agents: a real, isolated Android 13 phone or tablet that an agent drives over a plain HTTP API or an MCP server. It reads the screen, taps, types, swipes and installs APKs like a human user.

| Fact | Value |
| --- | --- |
| Website | https://eriusphone.com |
| Price | from $39/month |
| Free tier | No |

Vendor states there is no free tier and no free trial. A shared demo phone can be used in the browser for 90 seconds without signup, and early access currently takes no payment and no card because billing is not live yet.

## What it does

**Debugs and fixes** · Partly — It supplies the diagnostic evidence rather than a fix: your agent can pull a screenshot, the UI tree and Android's crash log at any step, but nothing changes your code.

> Today your agent pulls a screenshot, the screen's UI tree and the crash log at any step through the API.
> — https://eriusphone.com/ · How it works section, step 04 'Get results'

**Writes tests** · No — No test artefacts are produced: flows are given to the agent as plain-language goals, and the packaged pass/fail QA run is explicitly still unshipped on the Team plan.

> Coming soon: goal-based QA runs with reports
> — https://eriusphone.com/pricing.html · Plans section, Team plan feature list

**Done-for-you service** · Partly — You run your own agent against the API, but during early access the vendor's people set up each device and issue the API key by hand rather than self-serve.

> During early access we provision your dedicated Android device by hand and hand you its API key — running in its own isolated environment.
> — https://eriusphone.com/ · How it works section, step 01 'Get your agent's phone'

## How much it does unattended

**Runs autonomously** · Partly — Your agent can run a whole flow unattended over the API, but account sign-ins are a deliberate human step and the agent never gets your credentials.

> Account sign-ins (Google and others) are done once by a person, by design. The agent works inside the session you set up and never handles your passwords or 2FA.
> — https://eriusphone.com/docs.html · Limits & caveats, 'Sign-ins are a human step'

**Multi-agent** · Partly — Several agents can hold keys and drive separate phones in parallel, but one phone serialises actions and shares snapshot refs between everyone driving it.

> UI actions on a device run in order, so a snapshot's refs stay valid for the next tap. Different devices run in parallel. Refs are shared by everyone driving the same device.
> — https://eriusphone.com/docs.html · Limits & caveats, 'One action at a time per phone'

**Agent permissions** · Partly — A key is scoped to its own account's devices and nothing else, but there is no finer control: no IP restriction, no per-action scoping and no expiry.

> No self-service keys. You cannot rotate or revoke a key yourself. Keys do not expire on their own, and a key cannot be limited to certain IP addresses.
> — https://eriusphone.com/security.html · Section 5 'What we do not do yet'

## Which models it runs on

**Claude** · Yes — The vendor's own MCP server turns the device into tools for Claude Code and Claude Desktop, so Claude-based agents drive the phone without glue code.

> An MCP server that turns your ERIUS PHONE device into native tools for Claude Code, Claude Desktop, Cursor, or any other MCP client.
> — https://github.com/Protremix/erius-phone-mcp · README, opening paragraph

**Model choice** · Yes — The product supplies no model at all: any framework or tool-calling LLM you choose can call the HTTP API, which is how the vendor frames its no-lock-in pitch.

> Your agent (any framework — LangChain, custom code, an LLM with tool-calling) decides it needs to do something in a mobile app.
> — https://eriusphone.com/ai-agents/ · How an agent uses the phone, step 1 'AI Agent'

_Not established: GPT, Open models_

## Where you use it

**In your editor** · Yes — Through the vendor's MCP server the device appears as native tools inside Cursor and the Claude desktop and CLI clients, configured via an mcpServers block.

> Put the same `mcpServers` block in `~/.cursor/mcp.json` to use it in all projects, or in `.cursor/mcp.json` for one project.
> — https://github.com/Protremix/erius-phone-mcp · README, 'Add it to your MCP client' → Cursor

**On the command line** · Partly — There is no product CLI; the terminal surface is curl against the HTTP API, plus the MCP package's own stdio executable you install yourself.

> This installs an `erius-phone-mcp` command at `~/.venvs/erius-phone-mcp/bin/erius-phone-mcp`.
> — https://github.com/Protremix/erius-phone-mcp · README, Install, Option B: pip

**In a browser** · Yes — A hosted dashboard shows your phones live and is where you do the human sign-ins; a shared demo phone is also pokeable in the browser without signup.

> Once you have a key, the [dashboard](/dashboard/) shows your phones live: sign in with the same key.
> — https://eriusphone.com/docs.html · Authentication section, 'Getting a key: not self-serve yet'

_Not established: In your pipeline_

## Whose machine it runs on

**Self-hosted** · No — Hosted only, and on a single vendor-operated server: devices run in the vendor's Helsinki data centre with no bring-your-own-infrastructure option on any tier.

> Everything runs on one server, in a Hetzner data centre in Helsinki, Finland.
> — https://eriusphone.com/security.html · Section 3 'Data in transit and at rest', At rest

**Open source** · Partly — Only the client side is open: the vendor's MCP server package is MIT-licensed on GitHub, while the device platform and API implementation are closed and hosted.

> An [MCP](https://modelcontextprotocol.io) server that turns your [ERIUS PHONE](https://eriusphone.com) device into native tools
> — https://github.com/Protremix/erius-phone-mcp · Repository header (MIT License) and README opening

## What it costs to run

**How it meters** · Yes — Flat monthly price per device, with the plan deciding how many phones you get; the vendor explicitly rules out per-minute or per-session metering.

> Starter and Team are fixed prices for the phone count shown above — no per-minute or per-session metering.
> — https://eriusphone.com/pricing.html · Pricing FAQ, 'How does billing work?'

**Free tier** · Partly — No free tier and no trial, and signup is by invitation rather than self-serve, but anyone can poke a shared demo phone for 90 seconds without an account.

> Not right now. Every phone is a real Android system running in its own container, so each one costs us real compute … You can try a live phone for 90 seconds without signing up
> — https://eriusphone.com/pricing.html · Pricing FAQ, 'Is there a free tier or a free trial?'

**API access** · Yes — The API is the product: one documented JSON over HTTP interface with key auth covering reads, gestures, app install and crash logs, usable from any language.

> Every Erius Phone device is driven through one small JSON API for AI agent mobile automation: read the screen, tap, type, swipe, press keys, open apps and install your APK.
> — https://eriusphone.com/docs.html · Docs intro, 'Your agent's phone, over plain HTTP.'

**MCP server** · Yes — The vendor publishes an MCP server over stdio exposing devices, screen reads, gestures, app control and crash logs as tools to any MCP client.

> The server speaks MCP over **stdio**. Point your client at `uvx erius-phone-mcp`, or at the `erius-phone-mcp` executable, and pass the environment variables above.
> — https://github.com/Protremix/erius-phone-mcp · README, 'Any other MCP client'

**Bring your own key** · Partly — Inference is always yours since the vendor ships no model and the API is plain HTTP, but the device itself cannot run on your own cloud or hardware.

> One small JSON API any agent framework can call.
> — https://eriusphone.com/about.html · How we build it, 'Plain HTTP, no lock-in'

## Buying it for a team

**A company can buy it** · Yes — A Team plan with multiple phones and keys and a custom Enterprise tier exist, and the terms bind the company when you sign up on its behalf.

> If you're using it on behalf of a company, you're agreeing for that company too.
> — https://eriusphone.com/legal.html · Terms of service intro

**Seat model** · No — Billing counts devices, not people: plans are priced per phone with a fixed device count, and no user seat, seat floor or seat ceiling is published.

> Simple plans, priced per phone.
> — https://eriusphone.com/pricing.html · Page heading, Pricing

**Pooled budget** · No — There is no shared balance to pool: each plan is a flat monthly fee for a fixed number of phones with no metered consumption behind it.

> The plan is a flat monthly price per plan, billed in advance, cancel anytime.
> — https://eriusphone.com/pricing.html · Pricing FAQ, 'How does billing work?'

**Admin controls** · No — There is no administrative layer to constrain the agent with: the API has no admin endpoint or master key, and keys cannot be scoped beyond the account.

> The API has no admin endpoint and no master key. Every key belongs to exactly one account.
> — https://eriusphone.com/security.html · Section 1 'How your phone is isolated', Between customers

**Audit log** · Yes — Every API request is written to an audit log with account, key fingerprint, IP, device and action, though bodies are excluded and retention is not yet fixed.

> Every API request is recorded in an audit log so we can operate the service, investigate problems and detect abuse.
> — https://eriusphone.com/legal.html · Privacy · 1, 'When you use the API'

**Single sign-on** · No — No SAML or OIDC anywhere: the dashboard is entered with the API key itself, there is no password and the vendor states no second factor exists.

> No second factor in the dashboard. The API key is the only credential.
> — https://eriusphone.com/security.html · Section 5 'What we do not do yet'

## What happens to your code

**Opt out of training** · Yes — Nothing on your device is used for training at all, so there is nothing to opt out of; the vendor also says it does not log what the agent types.

> We don't look through it, analyse it, or use it to train anything.
> — https://eriusphone.com/legal.html · Privacy · 2 'What's on your device'

**Data residency** · Partly — Jurisdiction is known but not selectable: every device and volume sits on one server in Finland, with no published alternative region on any tier.

> Everything runs on one server, in a Hetzner data centre in Helsinki, Finland.
> — https://eriusphone.com/security.html · Section 3 'Data in transit and at rest', At rest

**Getting out** · Partly — You can email for a copy of your data or for deletion of devices, but export is manual rather than self-serve and no retention procedure is defined yet.

> You can ask us for a copy of the account information and logs we hold about you, ask us to correct it, or ask us to delete your account and all of your devices.
> — https://eriusphone.com/legal.html · Privacy · 7 'Seeing, fixing and deleting your data'

**Certifications** · No — No SOC 2, ISO 27001 or claimed GDPR compliance; the vendor states plainly that it holds no certifications at this stage, while honouring data rights on request.

> No certifications. We hold no security or privacy certifications, and we do not claim compliance with any specific regulation.
> — https://eriusphone.com/security.html · Section 5 'What we do not do yet'

## Provenance

Every fact above comes from the vendor. Nothing here is independently corroborated yet.

## Coverage elsewhere

None recorded. Every fact above comes from the vendor and is not independently corroborated yet.

## What changed

- 2026-10-09 — Capabilities · Commercial terms · Free tier · Price

## Correcting this record

Anything marked "Not established" is a question we have not answered — it is not a No. If you represent ERIUS PHONE, or anything here is wrong or out of date, you can supply it with a source: the operations this site accepts from an agent are listed at https://theagentsindex.com/.well-known/agents.json — that catalogue needs no key to read, and each entry states its own auth.

Supplying evidence is free. Nothing that can be bought here changes what a field says, whether a gap is closed, or how this record is scored.