Texas Mobile Proxy API: Houston Lines for Scripts and QA
A Texas line from Mobile Proxies US is one SIM on AT&T, T-Mobile or Verizon in a device we run in Houston, assigned to one customer for the plan term. Scripts reach it as an authenticated HTTP(S) or SOCKS5 proxy, or over VLESS, and manage it through the account API: list, rotate, status. This page gives the geolocation behaviour of a Houston address, the carriers on the Houston rack, protocol and speed facts, and the prices and rules.
Geolocation of a Houston address
Country United States and state Texas are reliable on all three carriers. City: T-Mobile resolves to Houston most consistently; AT&T usually Houston; Verizon's Texas pool is regional, so an address can be listed under Dallas or another hub while the state remains Texas. Vendors disagree with one another at city level after carriers re-plan their blocks.
Assert country, region, mobile connection type and carrier ASN (AS20057 AT&T, AS21928 T-Mobile, AS22394 or AS6167 Verizon) in tests. Log the city. Use T-Mobile when the city must be Houston.
The line from a script
Call GET /proxies/my, select the Houston line by licence uuid, store host, ports and authentication_user in configuration. Rotate by GET on its rotation_link; confirm the new exit IP through an echo request through the line. Handle 404 from /proxy/status explicitly: it means the plan ended and the licence was released.
A single exit IP serves both the HTTP and SOCKS5 ports; SOCKS5 also carries UDP for QUIC, WebRTC and remote DNS. The VLESS link gives the same line as a tunnel for a local xray gateway or a phone client.
Carriers in Houston
All three carriers are present. T-Mobile for metro-accurate city readings; AT&T as a steady default; Verizon when a user report names it. One line, one SIM, one address at a time. Independent identities require independent lines, each with its own uuid and rotation link in the API.
Houston is a spread-out metro with mixed cell load; speeds vary with the cell as on any phone. The plan figures are upper bounds.
Protocols, speeds and 5G+
HTTP(S) and SOCKS5 with UDP; VLESS via the dashboard link. 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 5G lines: $2 a day, $5 a week, $15 a month or $45 per three months; 70 Mbps and above average download on selected 5G lines, not guaranteed; not on hourly plans.
Prices and plan 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, 5G $3 then $3 an hour, up to four hours, never auto-renews; hours paid count toward the day plan when the line is kept the full day. Card, PayPal, Bitcoin, USDT including TRC-20, Ethereum, Zelle and bank wire. Instant activation.
Data is not metered. Fair use: a heavy day is 60 GB in one UTC day, counted over the plan period; six heavy days are logged; 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 Texas jobs
QA of apps and web flows as a Texas mobile user; state-dependent pricing, tax and availability; reproducing Houston user reports on the right carrier; South-central mobile latency to hosting regions; verifying your own ads, listings and local pages as served in Texas. Your own accounts, within each platform's terms.
Texas proxy questions
My Houston line shows Dallas. Is that a fault?
No. Verizon's Texas pool is regional and databases can list a hub city; the state stays Texas. Use T-Mobile when the city must read Houston.
How do I rotate from a script without exposing the API key?
Use the line's rotation link: a GET on it rotates that line and needs no key. The licence uuid in it is the credential, so store it as a secret.
Can I move the Houston line to another metro?
Yes, free, with remaining time kept, from the dashboard or POST /proxy/move-location. The host and ports can change, so re-read GET /proxies/my afterwards.
Is there a data meter on the Texas line?
No. Only the fair-use rule for repeated 60 GB UTC days applies.
