Skip to main content
There is no dollar limit you can set on this surface today. You cannot set a limit that suspends a device or refuses the next one. That is worth stating first, because the alternative is a reader who assumes a cap is there. What follows is what actually bounds your bill. The honest answer to “how do I avoid a surprise bill” is a handful of existing limits rather than one switch.

What bounds your bill today

A per minute phone spends only what you paid in

Per minute phones run on a prepaid balance (see Billing modes). A phone is charged each minute from that balance, so you cannot spend more than you have added:
  • When the balance runs out, the phone ends. Nothing is charged to a card behind your back.
  • We email you about 10 minutes before the balance would run out, so you can add funds or return the phone first.
  • A top-up you open and then leave on the Stripe page closes, and nothing is charged for it.
  • Returning a phone stops its charge.
Nothing pauses the charge while a phone is rented to you, whether or not anything is using it, so return a phone when you are done with it.

Monthly mode removes the variable

A monthly device has no meter, no allowance and no overage: it is billed every 30 days, and running it all the time leaves the invoice the same. If predictability matters more than the arithmetic, that is the mode that gives it to you outright. Cancel order on the console’s Billing page stops the next charge. See Billing modes.

A lease frees a device you forgot

A lease expires on its own after 10 minutes, and it can be renewed, but no lease may live longer than 60 minutes from when it was acquired. A client that crashed stops renewing, and the device frees itself within 10 minutes. A lease decides who may act on a device. It is not what you are charged for: a monthly phone costs the same whether or not it is leased, and a per minute phone is charged for the minutes it is rented to you. Lease-metered billing is not sold. See Metering units.
A loop that keeps taking the device never lets it go, so no other organization can take it. People in your own org can still act on it beside the loop. If you write a retry that re-acquires on failure, give it a stopping condition and a ceiling on attempts. The same goes for a loop that releases the device and then goes on acting on it: a gesture on a device your organization no longer holds takes it again, and each new lease starts its own fresh hour.

A run carries its own budget

start_run takes two limits and both of them are real ceilings, not hints:
  • maxSteps, the number of frames the run may consume. The default is 50 per run, and your value can only lower it.
  • deadlineMs, an absolute wall clock deadline, also capped by the deployment and by your lease’s own expiry, whichever comes first.
A run that reaches either limit is refused its next frame rather than billed further. See Agent tier.

Reading what you have spent

Two reads, both on the hosted control plane, both needing only devices:read:
  • GET /v1/usage returns this billing period’s settled usage per device: measured active time with corrections already applied, how many leases it came from, and the minutes already reported to billing.
  • GET /v1/receipts enumerates what your org has actually done, newest first, with keyset paging.
Use get_receipt when you hold an idempotencyKey and need that one outcome back. Use GET /v1/receipts when the question is what happened at all. Two things to read carefully before you build a budget alarm on this. Only settled leases appear in usage, so a lease you are holding right now is not in those numbers: it is an account of what has finished, not a live meter. And reportedMinutes is absent until reporting has happened, which is not the same as zero. The console’s Billing page, console.phoneuse.com/usage, shows your usage and your orders.

What is on the way

A dollar limit you set yourself, that suspends a device when it is reached, is a roadmap item, not a shipped feature. The limits above are the whole of what bounds your bill today.