Skip to main content
Each device is billed one of two ways: monthly, billed every 30 days, or per minute, paid from a prepaid balance. The choice is per device, not per org, so a fleet can mix both. A single device runs exactly one mode, and a monthly device is never metered.
Rates on this page were checked on 2026-10-18. The canonical, always-current price list is phoneuse.com; if the two ever disagree, the site wins.

Rates

The per minute rate is for the phone on sale today. The console shows the exact rate, and the amount you would pay, before you start a phone. For a larger fleet, the Enterprise plan is priced on a call: book a call with our team. Both identifier columns are fields you can read off a device, in the list_devices and get_device response. backendKind names how a device is reached, but no device field says whether a cloud phone is monthly or per minute. You choose that when you get the phone. The console’s Billing page lists your monthly orders and your per minute phones. fidelityTier answers a different question: how input reaches the screen. Fidelity describes the mechanism, while price tracks the phone behind it, so do not read one column off the other. See Capabilities for both fields, and Device tiers for what the tier means.
You can buy a cloud phone on the spot from Add a phone (/devices/add) in the console. See Buy and drive a device.
The table above is the rate card, not the order form. What you can buy monthly is whatever GET /v1/skus lists: one entry per pair of sku and billing mode that this deployment holds a configured price for, with a price for each model. A pair with no price is absent from that list rather than shown without a number. A model whose price cannot be read right now stays in the list without a price or quoteId; it cannot be bought until a later read shows its price. Per minute phones are listed separately, by GET /v1/minute/catalog. Believe those two reads rather than this page.
Robot hand + iPhone: buy it in the console. In Add a phone, choose Robot hand + iPhone, pick how many you want and pay $149 a month per robot at checkout. We prepare it within 24 hours after payment. Your purchase receipt in the console shows the payment, not the delivery. The robot hand is not part of the API, MCP or CLI today: GET /v1/skus lists Cloud phones only.

Monthly

A flat price for the device, billed every 30 days. There is no meter, no allowance to watch, and no overage: run the device all the time and the invoice reads the same. Each model has its own 30-day price, which GET /v1/skus carries on each model row. Choose this when a device is in steady use, or whenever you want the bill to be a constant rather than a variable.

Per minute

No fixed fee. You pay from a prepaid balance, and a phone is charged for each minute it is rented to you, from the moment it is ready until you return it or the balance runs out. Waiting for a phone to get ready is free. Starting a phone takes one page in the console (Add a phone, then Per minute), or one call to POST /v1/minute/starts:
  1. You choose the phone and how many.
  2. When a phone starts, 10 minutes of its rate is held from your balance for it. At $0.024 per minute that is $0.24 per phone.
  3. If your balance already covers that, the phones start right away and you pay nothing at that moment.
  4. If it does not, you pay one Stripe top-up for only the missing amount, at least $5 and rounded up to the cent. The phones start once that payment is confirmed.
  5. If you leave the Stripe page without paying, that top-up closes and nothing is charged. You can start again whenever you like.
If a paid start cannot go ahead (the phone sold out, or the rate changed while you were paying), the money stays in your balance and the start says why. We email you about 10 minutes before your balance would run out, so you can add funds or return the phone. Unused balance is not refunded online; contact abdulla@phoneuse.com with any question about it. Per minute phones are started and topped up by an org admin, signed in to the console. An API key cannot start one. Choose this for bursty or exploratory work, where a phone would otherwise sit unused for long stretches of the month. Return a phone when you are done with it: nothing pauses the charge while it is rented to you.

Which one to pick

The break-even is arithmetic: divide the 30-day price by the per minute rate and you have the number of rented minutes that costs the same as those 30 days. Below that, per minute is cheaper. Above it, monthly is, and the gap widens as usage grows. If you do not know your usage yet, start on per minute. It is the mode that punishes a wrong guess least. A phone does not move between the two modes, so when you know your usage, start a phone in the mode that fits.

Agent steps are a separate axis

Steps consumed by the agent tier are counted independently of the device’s billing mode. A device on either mode can run agent tasks, and those steps are accounted for on their own axis. See Metering units. Steps are included in the device price today, and no separate step rate is published. The reasonable use ceiling is not a billing threshold you can cross into an overage. It is enforced as a per run step budget, and a run that reaches its budget is refused its next frame rather than billed more. The default budget is 50 steps per run, a deployment can set its own, and maxSteps on your request can only lower it. One org may have 4 agent runs going at once by default. See Agent tier for how each ceiling is enforced.

Accounts start paid

There is no self serve free tier. An org is billed from first use, and there is no trial that silently converts. Payments are not refunded, and devices are not returned online. If you have a question about a device or a payment, contact support at abdulla@phoneuse.com and we’ll help. A Cloud phone keeps its paid period, and Cancel order on the console’s Billing page stops the next charge. See Buy and drive a device. If you would rather buy from a browser than from code, the console does exactly that, on this same surface and at these same rates. It is not a separate product, and this page applies to it.