Arizona Mobile Proxy API: Phoenix Lines for Developers
An Arizona line from Mobile Proxies US is one SIM on AT&T, T-Mobile or Verizon in a device we run in Phoenix, assigned to one customer for the plan term. It is reached as an authenticated HTTP(S) or SOCKS5 proxy, or over a VLESS tunnel, and it appears in the account API as a licence with a uuid, a host and ports, and a rotation link. This page states what an Arizona address reads as, how the carriers behave from Phoenix, and how to wire the line into scripts and test harnesses.
How a Phoenix address geolocates
Country and state are reliable on all three carriers: a Phoenix line reads as United States, Arizona. The city field is where carriers differ. T-Mobile addresses most consistently resolve to Phoenix itself. AT&T is usually Phoenix with occasional regional readings. Verizon assigns addresses from a regional pool whose database entries can point to a hub elsewhere in the Southwest while the state remains Arizona.
A script should therefore assert country, region and ASN (AS20057 AT&T, AS21928 T-Mobile, AS22394 or AS6167 Verizon) and log the city rather than fail on it. When a job genuinely needs the city string to read Phoenix, T-Mobile is the carrier to buy.
The line as an API object
GET /proxies/my lists every line on the account; an Arizona line shows its uuid, carrier, city as sold, network tier, expired_date in UTC, host, http_port, socket_port, authentication_user and rotation_link. A GET on rotation_link requests a new address from the same carrier pool for the Phoenix gateway; GET /proxy/status?license=UUID returns the current exit IP while the change lands.
The base URL is https://cp.mobileproxiesus.com/backend/api_v1 and the key travels in the x-api-key header. There is one key per account; it should live in a secret store, never in source.
Carriers in Phoenix
All three carriers are on the Phoenix rack. T-Mobile gives the most metro-accurate geolocation and a wide pool per rotation. AT&T is a steady general-purpose choice with addresses the large consumer platforms see constantly. Verizon's addresses are regionally organised, which matters only for city-level tests, and its reputation among US consumer services is as ordinary as the other two.
If a user report names a carrier, match it. Otherwise pick by geolocation needs, and remember a free move to another metro keeps the remaining time if Phoenix turns out not to be the right vantage point.
Speeds, devices and protocols
4G lines read up to 25 Mbps download and 5G lines up to 50 Mbps, with the latency of a cellular link. The device is a 4G/5G USB modem, a cellular router or an Android phone, chosen at checkout. Both endpoints share one exit IP; SOCKS5 also carries UDP, which matters for QUIC, WebRTC and DNS-over-the-proxy tests. The VLESS link in the dashboard gives an encrypted tunnel for a local xray gateway or a phone client.
5G+ is an add-on for 5G lines at $2 a day, $5 a week, $15 a month or $45 for three months. It reads 70 Mbps and above average download on selected 5G lines and is not guaranteed; it is not sold on hourly plans.
Prices and terms for an Arizona line
4G: $5 a day, $29 a week, $66 a month. 5G: $6 a day, $33 a week, $77 a month. Hourly: 4G $2 for the first two hours then $2 an hour, 5G $3 then $3 an hour, up to four hours, never renewing; keep the line for the full day and the hours paid count toward the day plan. Activation is instant on payment by card, PayPal, crypto (Bitcoin, USDT including TRC-20, Ethereum), Zelle or bank wire.
Data is not metered. A fair-use rule covers lines moving 60 GB in one UTC day on repeated days of a plan period; the first six such days are logged, the seventh brings a warning, from the eighth the line is slowed to 20 Mbps until a clean UTC day passes, and from the tenth held at 18 Mbps for the rest of the period.
Typical Arizona jobs
QA of apps and web flows as an Arizona mobile user; checking state-dependent content, pricing and availability; reproducing a Phoenix user's bug on their carrier; latency measurements from a Southwest mobile client to candidate hosting regions; verifying your own listings and ads as they render in Arizona. All of it with your own accounts, within each platform's terms, at a human pace.
Arizona proxy questions
Does a Phoenix line always read as Arizona?
State and country, yes, on all three carriers. The city is most precise on T-Mobile; Verizon can show a regional hub while the state stays Arizona.
Can I rotate the Arizona line from a script?
Yes: a GET on the line's rotation_link, with no key; read the link from GET /proxies/my and keep it secret. Confirm the new exit IP before continuing.
What if I need a second state later?
Move the line to another metro from the dashboard. The move is free and the remaining time is kept; the host and ports can change, so re-read GET /proxies/my afterwards.
Is there a data meter?
No. Only the fair-use rule for lines moving 60 GB in a UTC day on repeated days applies, and ordinary development work does not approach it.