Florida Mobile Proxy API: Miami Lines for Automation

A Florida line from Mobile Proxies US is one carrier SIM in one device we run in Miami, assigned to a single customer for the plan term. It is an authenticated HTTP(S) and SOCKS5 proxy, a VLESS endpoint, and an object in the account API with list, rotate and status operations. This page gives the geolocation facts for a Miami address, the carrier differences, the protocol and speed details and the price list, in the order a developer needs them.

What a Miami address reads as

United States and Florida on all three carriers. City: T-Mobile resolves to Miami most consistently; AT&T usually Miami; Verizon can place the address at a Southeast regional hub while the state stays Florida. Latin America-facing teams often choose Miami because US consumer platforms serve their Florida variant here and because latency from Miami to the Caribbean and South America is short, but the address itself is a US carrier address and is treated as one.

Tests should assert US, Florida, mobile connection type and the carrier ASN; the city is a logged value, not an assertion, unless the line is T-Mobile and the job truly needs it.

Driving the line from the API

GET /proxies/my returns the Miami line with uuid, carrier, network tier, expired_date, host, http_port, socket_port, authentication_user and rotation_link. Rotate is a plain GET on rotation_link; on phone lines it replies in about a second and the new address lands 10 to 15 seconds later. GET /proxy/status?license=UUID is the thing to poll while a rotation lands.

The rotation link needs no key because the licence uuid in it is the credential, so store it as a secret. It suits cron jobs and third-party webhooks; the API key belongs in your backend's secret store.

Carriers in Miami

All three carriers are on the Miami rack. T-Mobile for metro-accurate city readings and a wide pool; AT&T as the steady default; Verizon when a report names it. Each line is one SIM and one address at a time; its HTTP and SOCKS5 ports share the exit IP. Independent identities need independent lines.

Miami cells are busy in the evenings and in the tourist season. Speeds vary with cell load as on any handset; the plan figures are upper bounds.

Protocols, speeds and 5G+

HTTP(S) and SOCKS5 with UDP on every line; VLESS through the link on the line's dashboard page, suited to a local xray gateway or a phone client such as Shadowrocket or Hiddify. 4G up to 25 Mbps download, 5G up to 50 Mbps. Device chosen at checkout: 4G/5G USB modem, cellular router or Android phone.

5G+ on a 5G line: $2 a day, $5 a week, $15 a month, $45 per three months, for 70 Mbps and above average download on selected 5G lines, not guaranteed, not on hourly plans.

Prices and rules

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; hourly 5G $3 then $3 an hour; four hours maximum per purchase; never auto-renews; hours paid count toward the day plan when the line is kept the whole day. Payments: card, PayPal, Bitcoin, USDT including TRC-20, Ethereum, Zelle, bank wire. Instant activation.

No data meter. Fair use: 60 GB in a UTC day is a heavy day; heavy days are counted across the plan period; days one to six are logged only; the seventh brings a warning; from the eighth the line is slowed to 20 Mbps until a clean UTC day passes; from the tenth it is held at 18 Mbps for the rest of the period.

Common Florida jobs

QA of consumer apps and checkout flows as a Florida mobile user; Spanish-language and LATAM-facing variants of US services as served to Florida; reproducing Miami user reports on the right carrier; latency from a Southeast mobile client to hosting regions; verifying your own ads and listings as rendered in Florida. Your own accounts, within platform terms.

Florida proxy questions