Poe Mobile Proxies: Test Bots and Subscriptions as a US Mobile User

Poe aggregates many models behind one subscription and lets creators publish bots. Which models appear, how points and plans are presented, and how the mobile app behaves all vary by market, and the US is the reference. Bot creators checking their own bot's first impression, developers testing a Poe server bot end to end, and QA engineers verifying the US mobile path need to look from a US mobile network. A Mobile Proxies US line is that: one carrier SIM in one metro, with an API for exit IP and rotation.

What differs by region and device

Model lineup and limits per tier can differ by market. Subscription pricing and the purchase path follow the store and the region. New features reach US accounts first. The mobile app gates some capabilities by platform. Sign-in from a hosting address draws extra verification; a carrier address shared with real subscribers does not.

A US cloud region passes the country check only. The connection type still says hosting, and consumer products route that differently. The line passes both.

Testing your own server bot end to end

A Poe server bot is your HTTP endpoint that Poe calls. The server side is machine to machine and belongs on your cloud address. The user side, where a person on a phone in Chicago opens your bot, sends a message and sees the response render, is where the line belongs. Put the Poe app in an emulator behind the SOCKS5 endpoint or the web app in a browser profile behind HTTP, and run your bot's test conversations from there.

Log the exit IP and carrier per conversation from the API. When a rendering difference shows up, the log says which network it came from.

Checking your bot's public page and first run

Creators want to know how the bot page, the description and the first exchange look to a new US user on a phone. Load your own bot page through the line in a mobile browser profile and run the first exchange once. This is your own content and your own account, well inside terms.

Do it at a human pace. Rotation between checks gives a second address in the same metro if you want to confirm the view is not address-specific.

Timing a server bot from the phone's side

A Poe server bot answers over server-sent events, so what the user feels is the gap between sending a message and the first token on screen, plus how the partial text repaints. Your server log sees only its own half. Run the app behind the line, record first-token time on the client, and join it to your server's timestamps for the same conversation.

If you maintain several bots, label each test line with POST /proxy/update-tags, for example the bot's handle; tags come back in GET /proxies/my, so a harness can pick the right line by tag instead of holding a list of uuids. Run one pass on a network_tier of 4G and one on 5G to see how much of the delay is radio and how much is your bot. A slow first token on both tiers points at your bot; a gap between them points at the radio. Keep the prompts fixed between passes, so the comparison stays about delivery.

Rotation and terms

Rotate between sessions with a GET on the line's rotation_link; wait for the new exit IP; then start the next session. Not during a chat.

Use your own Poe account and your own bots within Poe's terms. The line does not change subscription tier or points; it shows the US mobile experience of what you already have.

Setting up a Poe proxy on Mobile Proxies US

1. Buy a line in a US metro; 4G is sufficient for chat, 5G for image-heavy bots.
2. Pull endpoints and credentials from the API into your test configuration.
3. Route the app (SOCKS5) or web profile (HTTP) through the line and verify the exit IP.
4. Run your bot's test conversations and the subscription screen checks; record exit IP per case.
5. Rotate between sessions by API; move to another metro for free for a second geography.

Poe proxy questions