fidelityTier in
the device’s capabilities.
Every device is driven through the same MCP surface. There
is no separate path for one kind of device: you call the same tools, against the
same normalized coordinate grid, whatever tier a device is on.
The tiers today
Software
Input is sent inside the operating system, or through the cloud
phone platform’s channel. Every device you can reach today is on this tier.
HID
Input would arrive as hardware keyboard and pointer events from an
external dongle. The value is declared, but no device reports it.
physical. It belonged to
the robot hand + iPhone, which you buy in the console and our team prepares;
it is not part of the API, MCP or CLI. No device reports it.
A tier is not a price. Fidelity describes how input reaches the screen, and
price tracks the phone behind it, so the
software tier spans several
prices: a monthly cloud phone, a Real phone identity cloud phone and a per
minute phone are all on it. See Billing modes for the
crosswalk between phones, backend kinds and rates.Capabilities are per device, not per tier
Do not infer what a device can do from its tier alone. Calllist_devices and
read the capabilities block on each one.
Capabilities describe both directions:
- Actions: whether the device supports tapping, swiping, typing, key presses, and opening apps, and by which mechanism. Typing, for instance, may be native or may be performed key by key against the visible keyboard.
- Observations: whether the device can take screenshots, whether a UI tree is available, and whether captured frames can be referenced by later actions.
Coordinates are the same everywhere
Every device uses the same normalized grid: both axes run 0 to 1000 regardless of the real screen size. Bounds in theui_snapshot tree are already on that
grid.
This is what lets the same tap work across devices, and it is why moving a task
from one device to another changes the device you name and nothing else.
Regions
A cloud phone comes up on the mobile network of one country, and that country is its region. It decides which app stores and services see the phone as local, so a task that needs a phone in Japan needs a phone whose region is Japan, not a phone somewhere else pointed at a Japanese site. You choose the region when you buy. Each model on the price list (GET /v1/skus) that can be placed in more than one country carries a
regions list, each entry an upper-case ISO 3166-1 alpha-2 code (US, JP,
GB) with its own shipsNow. Send the code you want as region beside the
model on POST /v1/checkout-sessions, and the purchase records it: the
device is provisioned in that region or the order waits until it can be, and
GET /v1/fulfilments shows the code on the purchase. A code the model does not
list is refused before anything is charged.
Three things to know:
- Stock is per model per region. A model can be available in one country
and sold out in another, which is why each region carries its own flag
rather than the model carrying one for all of them. A region listed with
shipsNow: falseis still shown so you can see it exists, and a purchase naming it is refused until stock returns. - The list is the deployment’s, not the world’s. Which countries a
deployment places phones in is a decision its operator makes; the list you
see is that decision. A model with no
regionshas one place it can be, and there is nothing to choose. - If you send no region, you get the deployment’s default for that model. The default is one of the listed regions, and the purchase records no region of its own, so it can later be fulfilled from any available unit of the model.
Which models are on sale
Which models are on sale changes over time, so this site does not list them. Read the live list instead:GET /v1/skus for monthly phones, each model with
its price and whether it can be bought now, and GET /v1/minute/catalog for
per minute phones. Add a phone in the console shows the same list.